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
TL;DR on ZombieLoad: this is like L1TF, where the CPU is using "garbage" data during a fault instead of coercing to zero (except here it's data instead of addresses). It seems this is pervasive problem class across the design of Intel CPUs, not just a single instance.
Basically it seems their engineering teams have, until now, considered it acceptable to have known-to-fault instructions operate on *complete garbage*, ignoring *all* privilege rules, as long as they will never retire.
This is, of course, completely insane from a security perspective, and given that we're now acutely aware of speculation attacks, represents *many* different opportunities for leakage. L1TF and ZombieLoad are on a completely different class from Spectre/Meltdown.
So my recommendation at this point would be to avoid Intel CPUs for several years if you care about this sort of thing, and OSes *need* to implement hyperthread pair privilege boundary separation, since that's most of the attack surface.
i do find it particularly interesting that they're exposing 'clear microarchitectual buffers and caches' as part of an instruction's behavior now
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
