Reply to post: Re: timing attacks

Re: timing attacks

> Cant you just reduce timer accuracy for untrusted code and get all your performance back?

Note that this is currently being implemented as a software mitigation for Javascript in browsers.

https://blog.mozilla.org/security/2018/01/03/mitigations-landing-new-class-timing-attack/

Interestingly, they also needed to disable SharedArrayBuffer (shared memory between two threads). Because a second thread which is simply incrementing a counter in shared memory can be used to synthesize a high-resolution timer.

For native code this would effectively require forbidding (shared-memory) multi-threading.