Re:Privacy implications of the QUIC protocol [pdf]
by ivanblagdan on Saturday January 04, 2020 @03:16PM
(#21957160)
Yes, theres other ways to be tracked at the network level, sure. I don't see how that changes the discourse?
Beyond the straight technical implications, isn't it concerning that a single company can roll out its own protocol across the server and browser stacks, implicating 7% of web traffic? Would it be more concerning if the same company has certain interest in improving its tracking and data collection capabilities?
Also, I was expecting to find details around browsers implementing some form of network level partitioning at that link you posted, but failed. Care to spell it out for me?
Re:Privacy implications of the QUIC protocol [pdf]
by jasonhansel on Saturday January 04, 2020 @11:41PM
(#21959671)
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
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.
(Disclosure: I work on ads at Google, speaking only for myself)