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
This speculation saga just keeps getting worse and worse, which goes on to show that there's a huge disconnect between CPU designers and security researchers. This is the CPU equivalent of foo = bar[untrusted]; if (untrusted > bound) return 0; do_stuff(foo);. Who does that?!
"Let's use garbage bits for something, it's fine, we'll throw away the result later". No. No it isn't fine. Why the fuck would that ever be a good idea? If you can't take the fault immediately at least poison the garbage data with zeroes!
No design reviews too!
it's honestly not obvious that this is a bad idea other than in hindsight; I know I'd make the same mistake
I mean, actual professional cryptographers fucked up AES implementations with secret-dependent lookups, and you're talking about CPU architects, which are several layers of abstractions further from the problem here
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
