3 ms·
Kind of... We solved this issue like 35 years ago and then broke it again in the last decade. First CPU timing attacks allowed peeking at secret key generation
by viraptor 10y ago
Kind of... We solved this issue like 35 years ago and then broke it again in the last decade. First CPU timing attacks allowed peeking at secret key generation in shared environments. Then we got rowhammer which ignores your mapping. Now we got memory access timing attacks which allow probing kernel memory mapping and bypassing ASLR.
While you can't easily write into other processes anymore, the barrier is more of a suggestion again.
- hatsunearu 10y ago"ignores your mapping" is pretty generous considering rowhammer doesn't work on ECC RAM.
- viraptor 10y agoFrom https://en.m.wikipedia.org/wiki/Row_hammer https://en.m.wikipedia.org/wiki/Row_hammer > Tests show that simple ECC solutions, providing single-error correction and double-error detection (SECDED) capabilities, are not able to correct or detect all observed disturbance errors because some of them include more than two flipped bits per memory word But anyway - even if ECC was perfect at preventing the issue, lots of hosts do not use ECC. That includes practically every desktop.