TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

I’m harvesting credit card numbers and passwords from your site (2018)

31 点作者 elsombrero超过 3 年前

4 条评论

greenyoda超过 3 年前
For those interested, the original discussion from 2018: <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=16084575" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=16084575</a>
dane-pgp超过 3 年前
It&#x27;s worth noting that a takeaway message from this is &quot;A strict CSP policy would completely prevent this attack, as long as Chrome supports the `prefetch-src` directive.&quot;<p>Unfortunately the ticket for implementing that (or taking the implementation out from behind its flag) is still open and has just had its 4th birthday.<p><a href="https:&#x2F;&#x2F;bugs.chromium.org&#x2F;p&#x2F;chromium&#x2F;issues&#x2F;detail?id=801561" rel="nofollow">https:&#x2F;&#x2F;bugs.chromium.org&#x2F;p&#x2F;chromium&#x2F;issues&#x2F;detail?id=801561</a>
tn1超过 3 年前
This is a hard problem to solve. It seems to me the best way to mitigate most of the issues is to disallow developers to upload the built artifacts and instead have the repositories build them. That way, at least you can guarantee the source corresponds to the hosted artifacts. On the other hand, this now puts a huge burden on the package hosters to provide the infrastructure to compile everything. And forget about any oddball packages that require esoteric or picky tools
democracy超过 3 年前
Yeah that makes me wonder how many of such real bombs are quietly deployed in npm&#x2F;maven setups all over the world...