Live data from Hacker News

Mozilla research: Browsing histories are unique enough to identify users

zdnet.com

101–110 of 131 posts

Re: Mozilla research: Browsing histories are unique enough to identify users

#101

Who is able to get access to my browser history? I thought it was just my ISP/VPN, which can obviously track me better in other ways.

It's in the article. You can do some clever Javascript/CSS tricks to sniff the browser history. Browsers are not trying to block this.

Re: Mozilla research: Browsing histories are unique enough to identify users

#103
post #88

Earlier quoted context omitted.

If you want to be less unique on amiunique.org/fp 1. Visit the site 2. Delete your browser cookies 3. Refresh 4. Repeat the steps until you're less unique

Or you know, just block JS.

Congratulations, you just broke 90% of the modern web. Might as well go directly to Gopher.

Re: Mozilla research: Browsing histories are unique enough to identify users

#104

Earlier quoted context omitted.

Or you know, just block JS.

Congratulations, you just broke 90% of the modern web. Might as well go directly to Gopher.

Congratualations on never actually bothering to block JS and find out - you know, facts. From actually doing so over many years, and so from actual experience I'd say completely non-functinal sites are about 25%.

Re: Mozilla research: Browsing histories are unique enough to identify users

#105
post #97

As counterstrategy you can use tools like http://trackmenot.io/ "TrackMeNot runs as a low-priority background process that periodically issues randomized search-queries to popular search engines, e.g., AOL, Yahoo!, Google, and Bing. It hides users' actual search trails in a cloud of 'ghost' queries, significantly increasing the difficulty of aggregating such data into accurate or identifying user profiles. "

I use it as far as I can but it's stopped working in palemoon. The queries it produces aren't very intelligent when you see them and it wouldn't take much NSA/MI5 work to trim much of them out.

I think TMN could be a fair bit smarter.

Re: Mozilla research: Browsing histories are unique enough to identify users

#106

Earlier quoted context omitted.

Or you know, just block JS.

Congratulations, you just broke 90% of the modern web. Might as well go directly to Gopher.

A bit of selective whitelisting with umatrix keeps everything functional while massively helping with privacy.

Re: Mozilla research: Browsing histories are unique enough to identify users

#107
post #75
post #20

Earlier quoted context omitted.

I've started using decentraleyes, hoping to mitigate this issue

Use LocalCDN. A fork of Decentraleyes with many more resources for cache. https://addons.mozilla.org/en-US/firefox/addon/local-cdn-web...

You linked to local CDN, I think you wanted localCDN (no space).

Re: Mozilla research: Browsing histories are unique enough to identify users

#108

Earlier quoted context omitted.

Congratulations, you just broke 90% of the modern web. Might as well go directly to Gopher.

Congratualations on never actually bothering to block JS and find out - you know, facts. From actually doing so over many years, and so from actual experience I'd say completely non-functinal sites are about 25%.

I’d put the number quite a bit lower than that, probably comfortably under 10% of sites I interact with, though the trend is definitely upwards, drastically so among interactive things (which are probably worse than 50% broken these days).

Re: Mozilla research: Browsing histories are unique enough to identify users

#109
By looking at all the data available to untrusted sites (as seen in https://amiunique.org/fp) you can tell that Web is many many years away from being privacy conscious. List of fonts, canvas fingerprinting, timezone, OS, user agent... the list goes on and on. Those of us who are tech-literate know better than to create tech like this today, but there's just too much momentum (and shady interests) to hot-swap Web for something else.

Re: Mozilla research: Browsing histories are unique enough to identify users

#110
post #91

Earlier quoted context omitted.

Given the prevalence of CGN, especially in mobile / cellular internet, and the reality that mobile is first for a large number, the use of IPs as a primary key feels less likely these days than a decade ago. > A user cannot change her IP address with the same ease as she can change her software fingerprints. I dunno. It’s a lot easier for my less techie friends to reboot their router and get a new IP than it is to ta…

How static/deterministic are the CGNAT translations though? It is conceivable that when client A connects to a Facebook service with IP X and port P that the source IP and port observed by Facebook is always the same. In any case your ISP is probably logging all your DNS queries and all their dynamic NAT translations to a database, so couple REMOTE_ADDR with REMOTE_PORT and a timestamp and you can almost certainly be…

Good points, and there's a sibling comment which notes some of this as well.

One thing to note is that your ISP is absolutely going to be logging every flow, with (at the very least) the following details:

SRCIP, SRCPORT, TRANSLATED SRCIP, TRANSLATED SRCPORT, DSTIP, DSTPORT

As to how the translations are occurring, I've never actually managed a CGN platform myself, but based on my knowledge of other hardware, I suspect you're closer to the reality than I was, and it's likely that a SRCIP always results in the same TRANSLATED SRCIP, as that can then be installed in hardware trivially and no longer needs to traverse the punt/cpu path to lookup what the translation needs to be.

That does leave the system open to abuse though, depending on how quickly entries age out, as a single customer could easily open up 65k sockets in a very short span of time, effectively DoS'ing any other customers who are using the same TRANSLATED SRCIP if there are no free TRANSLATED SRCPORTs left that their translation can bind to. Then again, the risk of this could be perceived to be low, with a AUP that can handle this if it turns out to be a social rather than technical problem, so it could still be happening in the wild anyway.

This remains a good reminder for me to avoid speculating about topics I haven't thought too deeply about!

Post reply on HN