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
I get the pattern as a problem obviously. I don't understand why "rdrand and cpuid share a buffer" equals "all your keys are belong to us". Surely key generation is more than `rdrand rax`?
Nah, that's a perfectly valid way of generating keys. It's also a perfectly valid way of generating random nonces for ECDSA, which, if compromised, also reveal the private key (see: PS3)
OK, I do see how that could be an issue. I will do my level best to care about this.
I mean it just boils down to rdrand data should be private to the core that requests it, so sending it to other cores too is a bad idea (as proven here where people found a way to get at it). Doesn't really matter how bad the practical attack scenario is :)
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
