惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

博客园 - 叶小钗
Microsoft Azure Blog
Microsoft Azure Blog
Stack Overflow Blog
Stack Overflow Blog
Jina AI
Jina AI
Vercel News
Vercel News
H
Help Net Security
Martin Fowler
Martin Fowler
美团技术团队
云风的 BLOG
云风的 BLOG
Y
Y Combinator Blog
阮一峰的网络日志
阮一峰的网络日志
MyScale Blog
MyScale Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
博客园 - 三生石上(FineUI控件)
博客园 - 司徒正美
人人都是产品经理
人人都是产品经理
Engineering at Meta
Engineering at Meta
G
Google Developers Blog
Blog — PlanetScale
Blog — PlanetScale
MongoDB | Blog
MongoDB | Blog
宝玉的分享
宝玉的分享
小众软件
小众软件
T
Tailwind CSS Blog
WordPress大学
WordPress大学

LWN.net comments

tcmalloc's weird hack [LWN.net] Fixed? [LWN.net] mpd [LWN.net] Userspace AX.25 [LWN.net] RIP [LWN.net] My two cents... [LWN.net] pipx [LWN.net] Tragedy [LWN.net] A young man destined for glory [LWN.net] And 'less' won't let you search [LWN.net] A great loss [LWN.net] Sad and shocking news [LWN.net] Easy migration from Clementine [LWN.net] Sad coincidence [LWN.net] GNOME is actually usable thanks to Seth et al [LWN.net] Sad news :( [LWN.net] armhf supports preempt_rt [LWN.net] MusicBrainz accurracy [LWN.net] On open source maintainership [LWN.net] Let's stop here [LWN.net] Not a new thing [LWN.net] uv is indeed great pgmoneta Some comments on this on a Postgres blog feed [LWN.net] uv [LWN.net] going to Debian [LWN.net] Upgrading 64-bit-capable systems to 64-bit kernels? [LWN.net] Free Software foundations Maintainers can wait for code review but not for publish review? A reasonably extreme point of view [LWN.net]
*Either* "not a vulnerability", *or* embargo [LWN.net]
muase · 2026-06-12 · via LWN.net comments

I think for the entire debate – especially also given the increased amount of vulnerabilities LLMs are concurrently uncovering atm – it is important to remember that embargoes are an inherently bad thing:
Security embargoes are a nice newspeak way to say "we intentionally keep our users uninformed and rob them of any choice to be vigilant, apply mitigations, or make other decisions to protect themselves", which actually is a pretty evil thing if you think about it.

Now there are situations where it might be the lesser of two evils, namely if it is a) a high-risk vulnerability that b) cannot be reasonably mitigated in practice, and c) where you can be reasonably certain that the vulnerability is not yet known to potentially malicious third parties. In this case, an embargo can be a reasonable choice – but only if all three conditions are met. And even then it still has the inherent risk that you’re wrong about c).

Now in your scenario, we already fail at option a) – if the reporter is not even sure something actually is a security vulnerability, they definitely cannot assert that it is a high risk security vulnerability. Therefore, embargo or not shouldn’t even be a question here.