-
Notifications
You must be signed in to change notification settings - Fork 531
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTTPS allows user tracking by OCSP Servers #507
Comments
OCSP stapling prevents this, but server support is required. |
I assume stapling goes by browser's session, so it's a mitigation IMHO
And admins must enable it, e.g. digicert SSL Certificate Checker says:
Related: #267 |
Yes, HTTPS has privacy implications currently, because of OCSP. But indeed OCSP stapling is solving the issue. It will takes time before this is generalised, but not using HTTPS is way worse: it means any machine on the network between you and the website or service you’re using knows everything you do. I’d rather much prefer some CAs to known that I went to this website at this time than anything I’ve just described. One other thing you could do is disable OCSP while waiting for OCSP stapling to be widespread. Or disable it only when there is no stapling. But not sure if that is currently possible. Also regarding ressources delivered by CDNs, this is a different topic. Either disable fonts/js/css (generally or through uMatrix for instance) and/or use Decentraleyes. |
I'm no terrorist looking for tutorials about how to build bombs at home, at least I don't look for such information everyday. That said, I personally prefer not to be tracked by multiple actors while looking about personal, but very innocent topics, let's say music, sport or whatever. |
Here the Dailystar site is linked. As site opens, the browser queries an SSL Server (Amazon CloudFront).
See: zscaler article
As the page is loaded, CSS Files are also fetched through HTTPS via CDN: Cloudfront is queried a second time and also 1e100.net (Alphabet Inc.) is queried. So Amazon and Google know that the user opened this site at a specific time.
DNT respecting sites, if delivered through HTTPS, make DNT useless:
https://cabforum.org/pipermail/public/2017-June/011346.html
IMHO HTTPS must be used only when the request include passwords and other personal information, otherwise big actors will track users browsing with ease.
Related to: #102
The text was updated successfully, but these errors were encountered: