4 ms·
How many bits per second (or kbps, mbps, etc) of memory reading is possible with Meltdown when run from JS vs running natively? Somewhat related, is it possibl
by koolba 9y ago
How many bits per second (or kbps, mbps, etc) of memory reading is possible with Meltdown when run from JS vs running natively?
Somewhat related, is it possible to neuter the JS engines in Firefox or Chrome so that they don't JIT JS and would doing so have any real world impact on mitigating this attack? If it relies on speedy execution to be possible maybe a solution would be to have a NeuterScript extension that deliberately slows things down.
- lykr0n 9y agoTo do it fast enough will peg the browser to 100% cpu for that thread. Saw a demo on twitter where they were not reliably able to extract information from the browser. Native, as in not running inside a browser, has been shown to be able to extract information reliably. My guess is the extreme amount of overhead that is required to run JS in an isolated-ish way. I think the point is that a JS based attack, while possible, would be much use outside proof of concept
- captn3m0 9y agoRelated to your second question: both Chrome and Firefox are deliberately increasing resolution of performance.now APIs to reduce ease of precision timing attacks.