Only Firefox Spectre patches work

>Implications >In this presented research we were able to show that even with the implemented Spectre mitigations, we were able to: >Read speculatively accessed memory in Chrome at around 1 bit per second. >Read accessed memory in Edge (not speculatively accessed) at around 1 bit per second. >Read accessed memory in Safari (not speculatively accessed) at around 1 bit per second. Money quote: >We were not able use these techniques in Firefox, as they recently reduced the timer resolution to 2ms Source: https://alephsecurity.com/2018/06/26/spectre-browser-query-cache/ Now name me one good reason why people in here actually use Chrom(ium) Sure it is """only""" 1bit/s but that is enough if you know where to look. Especially that some people have their browser open for hours. If Google, Apple and MS push a fix they should at least not fuarrrk it up again.

I imagine the majority of lains turn off JS anyway.

talk about being inefficient at writing native extensions

no info for Opera?

>>4988 I used to but you can't properly navigate through posts and their replies if you do that.

>>4987 It's nice that firefox's spectre patches work, but in general firefox has more exploits. It always falls faster than chrome at competitions

>>4988 Not only disable the JS But running A53 quad core I'll give FF another try maybe But it was crashy on ARM when 57 landed Maybe it has improved some by now

>>5591 AliExpress botnet