3 ms·
How? The CPU only has instructions for AES-NI (not for the actual encryption scheme, nor for key generation) and it has to be deterministic or it won't decrypt
by quonn 12y ago
How? The CPU only has instructions for AES-NI (not for the actual encryption scheme, nor for key generation) and it has to be deterministic or it won't decrypt on the other side. The only thing I can think about is trying to leak information using timing attacks and I wonder if these can be introduced through microcode updates. I doubt it and besides the risk for Intel would be far greater than for any of the companies involved in PRISM.
- xnull2guest 12y agoWas the parent talking about RDRAND? In this case the randomness used by the machine for both cryptographic protocols and key generation could be compromised, making AES, implemented in AES-NI or otherwise, moot.