3 ms·
Except if you are into *BSD. In that case you might want to label it "selective disclosure" instead of "responsible disclosure".
by HugoDaniel 9y ago
Except if you are into *BSD. In that case you might want to label it "selective disclosure" instead of "responsible disclosure".
- blablabla123 9y agoYeah, if you're not using Linux/Windows/macOS, this sucks. I wonder what happens next. Either alternative OSs for Desktops/Servers will become less popular or people are moving away from Intel chips. Obviously Intel CEO's betted on the latter - stocks are a representation of the future value of a company. Last year I was already hoping that ARM Chromebooks would become more popular but in reality you cannot find them in any retail store.
- pyvpx 9y agoprobably because Intel doesn't look too fondly at companies who make ARM motherboards. I believe it's high time the long history of anticompetitive actions by Intel end, and their near/effective monopoly in major market segments be regulated.
- Xylakant 9y agoWell, since some of the BSD folks publicly stated that they’d ignore any embargo, that seems like a pretty predictable consequence. And in this case I understand that it took a while to develop workable mitigations. Immediate disclosure might have caused great harm.
- JdeBP 9y agoTarring all of the BSDs with the same brush is wrong, both in general and here specifically. There's also the matter of both Matthew Dillon and Theo de Raadt discussing this topic months or even years before Google Project Zero made its discovery. * https://news.ycombinator.com/item?id=16086047 https://news.ycombinator.com/item?id=16086047 * https://news.ycombinator.com/item?id=16074531 https://news.ycombinator.com/item?id=16074531 * https://news.ycombinator.com/item?id=16075744 https://news.ycombinator.com/item?id=16075744 Moreover, the OpenBSD people have made some remarks about how it was commentaries in Linux patches and discussions on LWN that actually let the cat out of the bag this time. * http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table http://pythonsweetness.tumblr.com/post/169166980422/the-myst... (https://news.ycombinator.com/item?id=16046636 https://news.ycombinator.com/item?id=16046636) * https://news.ycombinator.com/item?id=16084404 https://news.ycombinator.com/item?id=16084404
- tptacek 9y agoThe bugs Theo was talking about were unrelated to these ones.
- JdeBP 9y agoI did point to https://news.ycombinator.com/item?id=16074531 https://news.ycombinator.com/item?id=16074531 . However, it is also wrong to err in the other direction as you have and to say that they were unrelated. Others have already made this point in https://news.ycombinator.com/item?id=16075744 https://news.ycombinator.com/item?id=16075744 , which I also pointed to.
- inferiorhuman 9y ago> Tarring all of the BSDs with the same brush is wrong, both in general and here specifically. Is that actually being done? The FreeBSD team got notified (late), the DragonFlyBSD, OpenBSD, NetBSD teams did not get notified. Matt, of course, seems to have a patch already.
- loeg 9y agoTheo de Raadt (OpenBSD BDFL) does not represent FreeBSD in any way. FreeBSD's policy is to work with embargoes.