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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

US senator urges investigation into Google+ bug ‘coverup’

100 点作者 egusa超过 6 年前

4 条评论

tptacek超过 6 年前
What an embarrassment. Blumenthal should leave the performative infosec policymaking to his colleague Ron Wyden.<p>It is not and never has been a norm for SAAS vendors to disclose internal vulnerabilities that have not been discovered independently by third parties. Tens of thousands are found every year by internal teams and contractors at companies around the country, many of them far more severe than the G+ bug (which would probably win a sev:low on a real assessment, less impactful than an XSS bug). You hear about none of them.<p>A coherent argument that this is as it should be: <a href="http:&#x2F;&#x2F;flaked.sockpuppet.org&#x2F;2018&#x2F;10&#x2F;09&#x2F;internal-disclosure-boring.html" rel="nofollow">http:&#x2F;&#x2F;flaked.sockpuppet.org&#x2F;2018&#x2F;10&#x2F;09&#x2F;internal-disclosure-...</a><p>You can argue that things should be different for shrink-wrap software and hardware products, where vulnerabilities have a half-life and users need to be notified to patch. I won&#x27;t disagree, but I will note that the norm of <i>not</i> disclosing internal discoveries holds there as well.
评论 #18213228 未加载
评论 #18213424 未加载
评论 #18213550 未加载
评论 #18213444 未加载
评论 #18213364 未加载
评论 #18213316 未加载
garyfirestorm超过 6 年前
Sure. First hold Equifax accountable, then we&#x27;ll talk about Google.
评论 #18213025 未加载
评论 #18213132 未加载
评论 #18213494 未加载
评论 #18213133 未加载
knorker超过 6 年前
So not only should companies have to publish hacks, they also have to publish when they internally find a bug?<p>Do I also need to publish if I left my keys in the door for two hours, but nobody broke in?
评论 #18213115 未加载
评论 #18213262 未加载
评论 #18213368 未加载
评论 #18213388 未加载
Isinlor超过 6 年前
It&#x27;s a really shitty job by Google PR people. Who in their right mind would close product in response to a security vulnerability? It was bound to grow out of proportions.<p>Headlines like &quot;500 000 people at risk! The bug was so serious that Google shuts down their social network!&quot; just write themselves.