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
Intel: "Hey, you know what would be a great idea? If we reused the same shared buffer for CPUID and RDRAND output, and shared it across all cores, and always loaded the whole thing, not just requested data." Their security incompetence truly knows no bounds.pic.twitter.com/nBtfGLEroj
Like, look, if after all this you still buy Intel for any security application, that's basically negligence at this point. They clearly don't have the slightest clue what they're doing. They don't care. They have no formal security boundaries. It's held together by masking tape.
What paper are you looking at? Want to know more about the topic. Good morning btw
I mean this in all sincerity - why is this a problem?
Because now you're broadcasting extremely sensitive data (as in: all your private keys are belong to us) intended for one core to all cores. That breaks down the core isolation boundary, making the security as weak as hyperthread isolation. And we know that one is really weak.
These are also the people who made rdrand/rdseed virtualizable...
Wow. I can understand sharing CPUID, but putting cryptographically sensitive random data in the same buffer? Why?
Sorry, what did you say about Intel and bounds?
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
