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
Nope. *Neither* of the two Spectre issues is specific to memory reads. One is about leaks from mispredicted direct branches, the other is about mistraining the indirect branch predictor to leak. Neither specifies *what* you leak and the possibilities depend on code sequences.
The key point here is *branch misprediction*, not speculative execution. Speculative execution is the class of problem but branch misprediction is the specific situation that qualifies those specific vulns (as compared to Meltdown, which *is* about memory reads from the kernel).
so i guess meltdown should be "branchread" and spectre should be "branchleak" and "branchtrain"
Meltdown isn't about branches. These are the names I suggested (also you can call the whole class SEXYPETCAT: Speculative EXecution Yields Privilege Escalation Through Cache Attacks :P)https://twitter.com/marcan42/status/953876003486445568 …
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
