3 ms·
> How is anyone better off not knowing the details of a vulnerability that people are exploiting already? This question is strange. On the one hand, the disclo
by eganist 10y ago
> How is anyone better off not knowing the details of a vulnerability that people are exploiting already?
This question is strange. On the one hand, the disclosure scares users into switching to Chrome even though Microsoft asserts Edge offers protection. On the other hand, the disclosure actually does not disclose the details of a vulnerability that people are exploiting already.
Would you rather have had the disclosure include the exact vulnerability?
I've addressed your other questions surrounding the benefits and drawbacks in other threads. No point in re-hashing them.
- tptacek 10y agoNo, you can't move the goalposts like this. You just said Google should have waited to disclose until a complete fix was published. In asserting that, you must also assert you'd rather have Google disclose nothing than something.
- eganist 10y agoI would rather Google disclose nothing to the public until there's a fix, or at least until a far-further-along date than 7 days from the initial disclosure to Microsoft. Now that that's settled: I didn't move the goalposts at all. I called into question the inconsistency in your implied assertion that people know the details thanks to this disclosure: > How is anyone better off not knowing the details of a vulnerability that people are exploiting already? People do not know the details. The disclosure gave enough to inform those not privy on where to look. It did not inform the world as to the details of the issue. I'd rather Google have disclosed nothing because as I've stated in the vast majority of my other comments. My position hasn't changed: no one is benefited by a public disclosure here other than • Google (getting people to use Chrome as a defensive measure even though arguably Edge has this one covered), and • any unprivy malware authors who now know where to look. Microsoft isn't going to act any more quickly here. Security vendors are already rolling out mitigations. Google's only advice was "use our browser" even though there are multiple solutions, both in terms of software (Edge) and advising on user actions for the general untargeted population. They included nothing other than: > Chrome's sandbox [...] prevents exploitation of this sandbox escape vulnerability. You asserted that they disclosed the details, which Google did not. So now that my position is set clearly in stone without you able to turn it around with an argument about moving goalposts, let's get back to my current question: Since you asserted that Google disclosed the details even though they did not, would you rather have had the disclosure include the exact vulnerability? Edited for formatting.
- tptacek 10y agoLots more words, but we're back to the exact same place we were before: there's active exploitation of the bug, and you think Google should hide that fact to give Microsoft breathing room. That is an... unorthodox position to take.
- eganist 10y ago> you think Google should hide that fact to give Microsoft breathing room. https://news.ycombinator.com/item?id=12842909 https://news.ycombinator.com/item?id=12842909 I have full confidence that one of the most mature software security groups in tech isn't looking for breathing room on an 0day. Since you've been scouting out my posts, you know better than to put words in my mouth given that one of my biggest assertions here is that Microsoft's already moving as fast as it can and that a disclosure speeds nothing up here. > Lots more words I appreciate the attempt at a dodge, so I'll get right back to it: since you asserted that Google disclosed the details even though they did not, would you rather have had the disclosure include the exact vulnerability?
- tptacek 10y agoI would rather have what we got than nothing. You would rather have nothing. I still don't understand your argument.