Re: Browser tracking
"Sebastian Geerken" <[email protected]>
| Newsgroups | gmane.comp.web.dillo.devel |
|---|---|
| Message-ID | <[email protected]> |
On Mo, Sep 08, 2014, Jorge Arellano Cid wrote: > Hi, > > This site is interesting. It gives kind of a score of web browser > trackability. [1] > > @corvid, I thought you'd like to give it a look (AFAIR, you have submitted > some standardizing to our HTTP querying in the past). It looks like > our HTTP_ACCEPT and "User Agent" are the most vulnerable to tracking. > > It looks simple to provide some less unique alternatives in dillorc. > > [1] https://panopticlick.eff.org/ I once started to read the paper (stopped where the math gets too complcated ;-) ); I remember that it is relatively simple to track a browser even if the browser fingerprint, which consists of numerous attributes, changes slightly when only few attributes (e. g. browser version) change. This gave me a vague idea to randomize these attributes exactly in a way to break re-detection. Dillo could perhaps be a good testbed for this. > DISCLAIMER: this is just on little aspect of the privacy chain. > Most probably this is moot unless you're behind a TOR ring. YMMV. For what I've understood, TOR wouldn't help. Sebastian _______________________________________________ Dillo-dev mailing list [email protected] http://lists.dillo.org/cgi-bin/mailman/listinfo/dillo-dev
signature.asc
(application/pgp-signature, 490 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBAgAGBQJUDgaOAAoJEAw7+YHB+ZL6NxoIALNmfMazygWQdsyTJh6v2HGY KTkWgTJzmjjpkJaLcZocBvyt4NsikZEOIiNOyqhiDzxD4yj4W4CPA51fBFm5hASF 7mYgS5xOGUeX8eajPME2YFy1az8/xAzmJZssIm12P1MA4f2faxqfbjdK8RXereSn +wGek30leD3rZHNFXMRT/jxhhp+kFVWxPLs/yA5zCCpfS5ZbGogKsuoPJAMgJgGI QWxNkqVbhxiy0kSdId0b3DsoTLRKiH/9vAQ7I9LTWfm1F4xE/e7LI7gAdJ1/5HR7 l64dlZDE/V1UP1lRLXeym9LjW2MQzQ90Tnrh8LSOm/B13ky3QlqYhD8saE7zUiU= =Wp/7 -----END PGP SIGNATURE-----