4 ms·
> ESXi has never had a security vulnerability due to this optimization, AFAIK. Should be vulnerable to FFS, if I'm not mistaken: http://arstechnica.com/securit
by creshal 10y ago
> ESXi has never had a security vulnerability due to this optimization, AFAIK.
Should be vulnerable to FFS, if I'm not mistaken: http://arstechnica.com/security/2016/08/new-attack-steals-private-crypto-keys-by-corrupting-data-in-computer-memory/ http://arstechnica.com/security/2016/08/new-attack-steals-pr...
- deleted 10y ago[deleted]
- derefr 10y agoTrue! Rowhammer-based attacks are kind of unique, though; I expect they'll be treated as a hardware bug and solved by releasing better hardware, rather than through inventing even more layers of securinoia to keep in mind from now on. It's sort of like when WebGL was first getting going, and the GPUs of the time didn't expect to be fed shaders directly from potentially-malicious web sources. Rather than severely restricting the WebGL API, we got a new generation of GPUs that fail safe.
- creshal 10y ago> I expect they'll be treated as a hardware bug and solved by releasing better hardware When Rowhammer was first announced, people said "it's okay, we have ECC". Then ECC was shown vulnerable. "It's okay, vendors have promised to fix it in DDR4", they said. Now DDR4 is out and vendors have not deployed the fixes systematically[1] and you have to benchmark every single RAM stick to make sure you're not vulnerable. I'd really appreciate software workarounds as long as hardware vendors keep fucking up. [1]: http://www.passmark.com/forum/memtest86/5395-rowhammer-mitigation http://www.passmark.com/forum/memtest86/5395-rowhammer-mitig...