3 ms·
I'm worried about the performance impact on low end intel chips like Atom/Celeron found in Chromebooks.30% hit will make computing on those platforms miserable.
by Abishek_Muthian 9y ago
I'm worried about the performance impact on low end intel chips like Atom/Celeron found in Chromebooks.30% hit will make computing on those platforms miserable.
Talking about chromeOS, is there any speculation about the impact of bug? Does it's hardened sand-boxing techniques put it in a better position even if KASLR is compromised?
- mtgx 9y agoHonestly, that serves Google right. I've been saying it for years how stupid Google is for encouraging 99% of Chromebooks to be powered by Intel chips (even more than Windows machines), when the Chrome OS itself is architecture-agnostic (for the most part). It was just stupid through and through. Even today we see ARM coming to full versions of Windows, but Google is still kicking it with Intel CPUs.
- dannyw 9y agoThe bug isn't really KASLR, it's more about reading kernel memory from userspace through side channel attacks of speculative execution. KASLR is/was the cover for the kernel patches, to avoid disclosing the real bug.
- Abishek_Muthian 9y agoThe comment in linux kernel mailing list, does pin point attacks using 'speculative execution' but isn't access to kernel memory space by any means a potential hazard to the security depending upon KASLR?
- svet_0 9y agoIndeed, kernel memory read seems more likely than address only read, the memory probably needs to be cached (in L1 maybe?). Attack is a timing attack as can be seen in this very interesting tweet - https://twitter.com/brainsmoke/status/948561799875502080 https://twitter.com/brainsmoke/status/948561799875502080