3 ms·
https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html https://security.googleblog.com/2018/01/todays-cpu-vulnerabi... https://goog
by johncalvinyoung 9y ago
https://security.googleblog.com/2018/01/todays-cpu-vulnerability-what-you-need.html https://security.googleblog.com/2018/01/todays-cpu-vulnerabi...
https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html https://googleprojectzero.blogspot.com/2018/01/reading-privi...
Seems that Google/Project Zero felt the need to go ahead and break embargo. Worth adding to the above list of news sources.
- victorhooi 9y agoNo, that's not accurate. If you read the article you quoted: > We are posting before an originally coordinated disclosure date of January 9, 2018 because of existing public reports and growing speculation in the press and security research community about the issue, which raises the risk of exploitation. The full Project Zero report is forthcoming (update: this has been published; see above). Just from public Gooogling, I believe it may have been the Register who tried to get in on the scoop, and broke the embargo: https://www.theregister.co.uk/2018/01/04/intels_spin_the_registers_annotations/ https://www.theregister.co.uk/2018/01/04/intels_spin_the_reg...
- lmm 9y agoNo-one necessarily broke the embargo. A blogger noticed unusual activity around a certain linux patchset and put two and two together, and the register mostly sourced from his article ( http://pythonsweetness.tumblr.com/post/169166980422/the-mysterious-case-of-the-linux-page-table http://pythonsweetness.tumblr.com/post/169166980422/the-myst... )