Mozilla is literally turning off SharedArrayBuffer effective immediately because of the kernel memory bug D:https://twitter.com/migueldeicaza/status/948715833605459969 …
-
-
Replying to @mcclure111 @antumbral
Not just Mozilla, Chrome too, and probably the others. It's because SharedArrayBuffers could be used to implement a high res timer.
2 replies 3 retweets 9 likes -
I don't know anything here, but if you can repeat the attack as many times as you like could you use statistics to do the timing attack with a lower res timer?
2 replies 0 retweets 3 likes -
Replying to @moocowpong1 @Tojiro and
Yes. Lowering res will not stop timing attacks, just slow them down. To stop them you need to falsify time in a way that doesn't preserve statistics, or eliminate time.
1 reply 0 retweets 7 likes -
Replying to @RichFelker @moocowpong1 and
"To fix this massive, worldwide computer bug we must eliminate time." <-- I want to see this episode of Doctor Who, like, yesterday.
2 replies 21 retweets 48 likes -
Replying to @Tojiro @RichFelker and
Two of the biggest reasons for http://performance.now are animation and games, and if browser vendors had a proper frame scheduling mechanism we wouldn't need it for those
1 reply 0 retweets 4 likes
If you had frame scheduling you could use it along with busy loops to reconstruct time.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.