|
|
|
|
|
by gioele
4308 days ago
|
|
WRT the AESNI leaking information in the XMM registers, wouldn't starting a fake AES decryption solve the problem? Also, wouldn't a wrapper function that performs the AES decryption and then manually zeroes the registers be a good enough work around? |
|
Yes, you probably ought to be clearing xmm* registers touched by it, and that would I hope be good enough.
The point in the article about compiled code very seldom touching xmm* so that if you don't wipe it - is doing so currently common practice? I haven't checked, but I feel like that would be something that needs checking! - it's hanging around and you might leak it, is completely valid, however.