Meltdown, aka "Dear Intel, you suck" reddit / BSD ---------------------------------------------------------------------- masta · 2018-01-06 17:52 Yeah, it's disappointing Intel wasn't able (or unwilling) to notify all the OS providers. There was a big concern about the information leaking early, which actually happened. So perhaps Intel was justified in limiting access? ---------------------------------------------------------------------- fupjack · 2018-01-06 21:40 I think you mean "unjustified". ---------------------------------------------------------------------- [deleted] · 2018-01-06 22:25 I think you mean "behaving as Intel usually does when somebody exposes their shitty microcode" ---------------------------------------------------------------------- [deleted] · 2018-01-06 22:25 [deleted] ---------------------------------------------------------------------- rootwyrm · 2018-01-06 23:09 I think you mean "behaving as Intel usually does." ---------------------------------------------------------------------- [deleted] · 2018-01-06 23:12 [removed] ---------------------------------------------------------------------- [deleted] · 2018-01-06 23:12 [deleted] ---------------------------------------------------------------------- MaoTseDamnSon · 2018-01-07 03:43 My people!! ---------------------------------------------------------------------- TheEdgeOfRage · 2018-01-07 13:11 What's the point of keeping it secret then if you're not going to tell the people who need to fix stuff. And besides, OpenBSD devs are one of the most dedicated people to security, so if you can't trust then, who can you trust? ---------------------------------------------------------------------- malcontnet · 2018-01-07 14:42 > There was a big concern about the information leaking early, which actually happened. Wasn't the "leak" just caused by Linux kernel code made public? I might be uninformed on the matter but wasn't it that Linux was the only OSS project informed by Intel and/or Google (probably because Android is Linux-based)? Then instead working on the source quietly, these sources were put on git/web/whatever so everyone could see the changes? My pov is that they told 2 biggest closed-source OS players (Microsoft and Apple) and one OSS project (to help themselves) and shat on every other OS' user. I'm feeling shat on by both Google and Intel. ---------------------------------------------------------------------- masta · 2018-01-07 15:28 Not sure openbsd was relevant to Intel, unlike FreeBSD which has a relevancy in the PS4 and Apple. I'm not trying to disparage OpenBSD, it's wonderful and I'm sure the devs are trust worthy, and certainly able to sign the non disclosure agreement. ---------------------------------------------------------------------- TheEdgeOfRage · 2018-01-07 15:38 FreeBSD is also used by many services like Netflix. So I can understand that, but it's still not a reason to not give the OpenBSD devs a heads-up as well. ---------------------------------------------------------------------- masta · 2018-01-07 15:41 The person who implemented the proof of concept was using an Apple laptop, so not Linux. But there were some commits to Linux, and they were NOT indicative of any security issue at all. So it's unlikely story, probably to cover up somebody leaked the info early. Also it would have taken a long time to implement and get it working. For example the security researchers who discovered the problem have only been able to get it working once, and not again (supposedly). So it was leaked very early, and that is why these are not shared so widly. Because people talk, and want to share secrets. ---------------------------------------------------------------------- masta · 2018-01-07 16:24 The same argument can be made for templeOS. ---------------------------------------------------------------------- tidux · 2018-01-07 20:44 > But there were some commits to Linux, and they were NOT indicative of any security issue at all. [One guy figured it out.](http://pythonsweetness.tumblr.com/post/169166980422/the- mysterious-case-of-the-linux-page-table) From there it went to /g/, then to /r/sysadmin, then The Register and other media. It was in fact due to the Linux kernel patches. ---------------------------------------------------------------------- [deleted] · 2018-01-08 02:51 [deleted] ---------------------------------------------------------------------- masta · 2018-01-08 03:05 And, apparently.... given how the Linux community failed to secure the issue at hand, I'm still unconvinced how the BSD community would have handled it any better? Still I'm pretty sure the leak happened due to insider knowledge. ---------------------------------------------------------------------- UninsuredGibran · 2018-01-08 07:13 Indeed, and in fact for anyone developing code for Intel chips.