Comment by mx7zysuj4xew
14 hours ago
You don't seem to understand how this works
An exploit can only "leak" if it's a private 0day used by APTs.
When warnings are sent out it has already been a public fact. Keeping some kind of dumbass embargo is just pointless theatre
"Windows 11 has a critical vulnerability."
Boom. A leak. It's now a public fact, so we'll instantly see people exploiting it, right? Except that without a commit or patch fixing it, or even a suggestion of a workaround, you are searching for a needle in a haystack. It could be literally anywhere, after all!
In fact, it is so well-hidden that I have not even discovered it myself yet. But its presence is a statistical certainty due to the sheer size of the codebase, so we should assume it is somewhere in there. Did I just doom every W11 user, or are perhaps embargoes at least somewhat useful?
You're missing the point
> I feel like all "non-inner-circle people" here are taken for a laugh. OpenAI and these security companies sat on this for 2 months, decided for themselves who gets access to an early fix, and then leave the rest out to dry
Had they just kept this between themselves and the vendor this would've been effective.
Instead they selectively released it to various parties one of which promptly leaked it.
This is exactly what should have been expected
Either it's 100% silent or it's out there