Spectre/Meltdown nominated for most over hyped bug at Pwnies
pic.twitter.com/TVJ8OXXFRy
Yeah, I do @musllibc, FOSS & infosec stuff. But now is not the time for a mostly-/only-tech Twitter feed.
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Add this Tweet to your website by copying the code below. Learn more
Add this video to your website by copying the code below. Learn more
By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.
| Country | Code | For customers of |
|---|---|---|
| United States | 40404 | (any) |
| Canada | 21212 | (any) |
| United Kingdom | 86444 | Vodafone, Orange, 3, O2 |
| Brazil | 40404 | Nextel, TIM |
| Haiti | 40404 | Digicel, Voila |
| Ireland | 51210 | Vodafone, O2 |
| India | 53000 | Bharti Airtel, Videocon, Reliance |
| Indonesia | 89887 | AXIS, 3, Telkomsel, Indosat, XL Axiata |
| Italy | 4880804 | Wind |
| 3424486444 | Vodafone | |
| » See SMS short codes for other countries | ||
This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.
Hover over the profile pic and click the Following button to unfollow any account.
When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.
The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.
Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.
Get instant insight into what people are talking about now.
Follow more accounts to get instant updates about topics you care about.
See the latest conversations about any topic instantly.
Catch up instantly on the best stories happening as they unfold.
Spectre/Meltdown nominated for most over hyped bug at Pwnies
pic.twitter.com/TVJ8OXXFRy
I want to nominate Spectre for most underhyped, to the point the vendors don't even see it meriting a fix...
The chip vendors are adding speculation barriers, but the big problem is adding the required compiler analysis to figure out where to insert them. Requiring users to strategically sprinkle __builtin_speculation_safe_value (untrusted) around code is not an ideal approach.
That's not a fix. That's a pathetic tool for minimal workarounds on a case-by-case basis. A fix is an MSR to disable speculative execution across branches or entirely.
That’s what is being proposed. BTW Disabling all speculation is a big sledgehammer when it is possible to design CPUs that speculate without visible side effects.
I believe it's plausible to design a CPU that speculates without visible side effects, but it sounds difficult. I don't believe it's possible to add that via microcode. An MSR to disable all speculation should be possible as a microcode update.
and I believe even that approach needs microcode update; over CPU vendors are proposing other mechanisms to introduce these “speculation barriers”. If it were easy it would be easily fixed. There needs to be fundamental design changes for side-effect free speculation.
Fundamental design changes are needed to make it fast, specifically fast enough to be acceptable to most users. Just fixing it is trivial: nuke speculation.
Nuking speculation is only trivial if that is already “designed in”. Perhaps okay for new processors. The “speculation barrier” is what is on the table for current designs that may be able to be introduced by micro-code.
Nuking (all, not just BTB) branch prediction should also work (aside from meltdown I'm not aware of other ways speculation could be exploited, but not 100% sure) and seems likely to be possible with microcode.
If neither is possible, vendors should be offering compelling technical explanations of why it's not possible rather than refusing to even speak about it. The appearance is that they DON'T WANT TO FIX IT in any way that would look bad wrt performance.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.