3 ms·
Browser fingerprinting is a hack, and exploits clear loopholes in browser privacy models. I wouldn't rely on it because it's committing to an ongoing arms race
by simonw 7y ago
Browser fingerprinting is a hack, and exploits clear loopholes in browser privacy models.
I wouldn't rely on it because it's committing to an ongoing arms race against the browsers. One that I expect them to win.
- thenewnewguy 7y ago> I wouldn't rely on it because it's committing to an ongoing arms race against the browsers. One that I expect them to win. Don't be so sure about this. The world's most popular browser is developed by the world's largest advertising company. I'm not saying Google is intentionally sabotaging Chrome, but I doubt they're putting significant resources into anti-ad technologies.
- contravariant 7y agoWell, in the end it's their competitors that are hurt most when they close loopholes without warning. All chrome needs to do is hamstring ad-blockers (which they just did) and add a fingerprint that only google can use (like tying your google account to the browser for no reason...)
- nordsieck 7y ago> Browser fingerprinting is a hack, and exploits clear loopholes in browser privacy models. > I wouldn't rely on it because it's committing to an ongoing arms race against the browsers. It doesn't seem to me that browsers are trying to win at all. For example, one of the greatest discriminators - font list - has been known about since people were talking about browser fingerprinting. The fix would be pretty easy too: in incognito mode (or when toggled by the user), only support 2 fonts: 1 serif and 1 san-serif that ship with the browser on all platforms. I don't think any of the browsers want to do that. There are a number of other longstanding fingerprinting issues that are similarly easy to fix.
- bzbarsky 7y agoLast I checked, Safari in fact restricts the fonts web pages can see/use to ones that ship by default with MacOS. So you can't fingerprint a Safari user via fonts any further than "Safari user". So yes, browsers, at least some of them, are in fact trying to win here.
- kevin_thibedeau 7y agoYou'd need a standardized font rendering engine to defeat fingerprinting via canvas.
- michaelt 7y ago"Same canvas image looks the same on every browser" seems like a desirable state of affairs to me?
- Buge 7y agoI think the problem is that canvas can be GPU-accelerated, and GPUs don't have an exact standard for how each pixel will look.
- nordsieck 7y ago> You'd need a standardized font rendering engine to defeat fingerprinting via canvas. That's fair. But that really only gives the attacker the OS (and perhaps the GPU vendor?). Not ideal for sure, but not that many bits of info, especially if you are in the majority (windows / intel)
- tyingq 7y agoDoesn't Google have to leave a Chrome loophole for themselves that is less conspicuous than a specific exception for DoubleClick/Google?
- londons_explore 7y ago> One that I expect them to win. Sure, the basic things like "which fonts do you have installed" are easy to make consistent, but there are thousands of other ways to fingerprint a browser, many of which would have serious performance impacts if fixed. For example, Macbook Air's can only run at full CPU speed for about a second before slowing down. Just make a 2 second javascript busy loop and watch for the slowdown. Are you going to slow all users down all the time just so these macbook users can't be identified?