3 ms·

It's really difficult, though. There are dozens of different ways someone can be fingerprinted [1], and you may have to make serious or even crippling changes t

It's really difficult, though. There are dozens of different ways someone can be fingerprinted [1], and you may have to make serious or even crippling changes to browser features to mitigate some techniques. It's not fair to say "privacy is dead", but I think it's safe to say "browser fingerprint evasion is dead". Solutions to easily and selectively block unsavory companies and networks (ad or otherwise) while letting users allow some things, like uBlock and uMatrix, are probably the only feasible solutions. [1] https://www.chromium.org/Home/chromium-security/client-identification-mechanisms https://www.chromium.org/Home/chromium-security/client-ident... (This still isn't a totally comprehensive list)

deleted 11y ago
[deleted]
- deleted 11y ago
  [deleted]
- deleted 11y ago
  [deleted]
- jtuchsen 11y ago
  Do you have an example of this working? I thought that browser venders we're having the :visited selector lie to you when you call getComputedStyle on them? Also, how would you workaround the need for JS? I understand that you can do something similiar with tracking pixels, but I'm under the impression that Ghostery blocks them.
  - anon1385 11y ago
    >I thought that browser venders we're having the :visited selector lie to you when you call getComputedStyle on them? It's possible to probe the users history even though getComputedStyle doesn't give it away anymore. See page 6 of this article: http://www.contextis.com/documents/2/Browser_Timing_Attacks.pdf http://www.contextis.com/documents/2/Browser_Timing_Attacks.... Obviously turning off Javascript prevents these types of things to some extent, but even then there are ways: https://www.nds.rub.de/media/nds/veroeffentlichungen/2014/07/09/DSN_paper.pdf https://www.nds.rub.de/media/nds/veroeffentlichungen/2014/07... The web is just not designed with preventing information leaks in mind.
    - jtuchsen 11y ago
      Interesting papers, thanks for calling my attention to them. They made me paranoid enough to disable the styling of visited links in Firefox to prevent the large amount of timing attacks that are possible.

deleted 11y ago

[deleted]

deleted 11y ago
[deleted]
deleted 11y ago
[deleted]
jtuchsen 11y ago
Do you have an example of this working? I thought that browser venders we're having the :visited selector lie to you when you call getComputedStyle on them? Also, how would you workaround the need for JS? I understand that you can do something similiar with tracking pixels, but I'm under the impression that Ghostery blocks them.
- anon1385 11y ago
  >I thought that browser venders we're having the :visited selector lie to you when you call getComputedStyle on them? It's possible to probe the users history even though getComputedStyle doesn't give it away anymore. See page 6 of this article: http://www.contextis.com/documents/2/Browser_Timing_Attacks.pdf http://www.contextis.com/documents/2/Browser_Timing_Attacks.... Obviously turning off Javascript prevents these types of things to some extent, but even then there are ways: https://www.nds.rub.de/media/nds/veroeffentlichungen/2014/07/09/DSN_paper.pdf https://www.nds.rub.de/media/nds/veroeffentlichungen/2014/07... The web is just not designed with preventing information leaks in mind.
  - jtuchsen 11y ago
    Interesting papers, thanks for calling my attention to them. They made me paranoid enough to disable the styling of visited links in Firefox to prevent the large amount of timing attacks that are possible.