1/ Over the last few weeks, I've been studying microarchitectural timing attacks. Some highlights:
-
-
Replying to @McLean0
2/ Hardware implementation details are supposed to be hidden. The instruction set is a CPU's API.
1 reply 0 retweets 0 likes -
Replying to @McLean0
3/ If you measure how long operations take, CPU implementation details like caching, branch prediction are visible
1 reply 0 retweets 0 likes -
Replying to @McLean0
4/ Timing differences reveal information about the CPU's internal state.
1 reply 0 retweets 0 likes -
Replying to @McLean0
5/ Instruction sets are a leaky abstraction, where "leaky" means "sometimes leaks SSL keys".
1 reply 0 retweets 0 likes -
Replying to @McLean0
6/ Crypto code and other security-sensitive software is written carefully in a special way to prevent information leaks
1 reply 0 retweets 0 likes -
Replying to @McLean0
7/ I'm working on a Rust library to make this easy. More details soon!
1 reply 0 retweets 1 like
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.