[Taps on the forehead] You wouldn't get cache timing attacks for speculative accesses, if your CPU does not have nanosecond-scale timing measurement instructions. Or a cache. Or speculation. Or memory reads. Easy!
-
Show this thread
-
The government has to STEP UP and mandate RDTSC to be the privileged instruction, and revoke FIPS 140 validation from any system that provides unrestricted access to it!
4 replies 2 retweets 6 likesShow this thread -
Replying to @shipilev
This is true, but to mitigate you need to shut off access to time entirely, or cleverly falsify it, not just reduce resolution.
1 reply 0 retweets 0 likes -
Replying to @RichFelker
That was not-so-obvious joke, because you can always model time, with e.g. timed events, timeouts, heck even just something that monotonically increments a global counter. Timing measurement is extremely hard to restrict access to...
1 reply 0 retweets 0 likes
Pure-functional code obviously has no access to time, but yes, its a very restrictive assumption.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.