3 comments

[ 3.7 ms ] story [ 15.0 ms ] thread
TLBleed is not just extracting which pages of memory are touched but also in which order. How do you harden e.g. scrypt against this?
Maybe the answer is "wait and see the full details when they become available", but is there an example of code that is hardened against cache side channel attacks but would be vulnerable against TLB side channel attacks?
Symmetric MultiThreading (SMT) - that would be Simultaneous MultiThreading