The issue of using the browser cache to perform timing attacks, which you mentioned in the post above, has been known for two decades: https://sip.cs.princeton.

The issue of using the browser cache to perform timing attacks, which you mentioned in the post above, has been known for two decades: https://sip.cs.princeton.edu/pub/webtiming.pdf https://sip.cs.princeton.edu/pub/webtiming.pdf The fix you mentioned (getting rid of shared caching) is discussed in the above article from 2000. Genuinely surprised this hasn't been fixed earlier.