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
Seems like it’s time to put RDRAND out to pasture and just use RDSEED
What makes you think RDSEED doesn't go through the exact same bus and have all the same problems?
I’m just saying, use RDSEED to seed your preferred userspace CSPRNG and call it a day
(also RDSEED is mentioned as also being an instruction of interest in the paper so it probably *is* similarly affected. i just hope you're reseeding your prng significantly less often than reading it)
I'm not saying it doesn't. What I'm saying is that you don't need to use it frequently and so if it slows everything down to a halt when you sample it once a day, it's not the end of the world.
You're still screwed. If you're running untrusted code on another core: 1) without the mitigation, they can steal your secrets 2) with the mitigation, they can DoS your memory bus performance. The only solution is to not mitigate and not use RDRAND/SEED at all.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
