Live data from Hacker News

Race Is On to 'Fingerprint' Phones, PCs

online.wsj.com

31–40 of 42 posts

Re: Race Is On to 'Fingerprint' Phones, PCs

#31
post #22
post #17

Earlier quoted context omitted.

In my experience, there's enough basic information in the HTTP transaction to identify a unique visitor for most forensic purposes. However, the level of detail available for fingerprinting goes far beyond this. I just performed a little experiment, disabling as much as I could in Firefox to affect my uniqueness at http://panopticlick.eff.org/ . I was surprised when disabling plugins (font info comes from java & flas…

The more unusual your configuration, the more likely it is to be unique in the context of things you can't change. Most people don't run with all these things disabled...

Enough people do so that's it's not a set of something small like 10.

Re: Race Is On to 'Fingerprint' Phones, PCs

#32
post #26
post #17

Earlier quoted context omitted.

In my experience, there's enough basic information in the HTTP transaction to identify a unique visitor for most forensic purposes. However, the level of detail available for fingerprinting goes far beyond this. I just performed a little experiment, disabling as much as I could in Firefox to affect my uniqueness at http://panopticlick.eff.org/ . I was surprised when disabling plugins (font info comes from java & flas…

The thing about Panopticlick is that the two most "accurately" identifying methods aren't stable fingerprints. As soon as you install an update to one of your plugins (the constant Adobe updates come to mind), your fingerprint is altered. Similar with the font list; programs seem to be installing new fonts on my system all the time, which makes that fingerprint unstable as well.

Yes. If you wanted to get serious, you should deal with unstable characteristics. Perhaps with Bayesian filtering or something? And maybe adding some outside information, like when the new flash plugin is released; and tracking if a user is likely to upgrade or not.

If you have a working solution for unstable characteristics, you can also add more more characteristics, than they do at the moment.

My scree1050x3360x24

Re: Race Is On to 'Fingerprint' Phones, PCs

#33
post #2

Based on this article you can "fingerprint" a computer using the following combination of attributes: - Precise timestamp - Monitor size - User agent - Browser plugins - and fonts (!) Really?? I use several browsers, and switch out a few external displays for my laptop. Plugins come and go with the browser version. My system time is synced to a timeserver (as I imagine are many other computers) but sometimes not. Bas…

The EFF tested this themselves. They run a website, http://panopticlick.eff.org , comparing with computers that have visited in the past. They have over a million fingerprints at this point, and my Chrome install is "unique." It displays all data it lifted from your machine, along with how rare each datum appears to be. On my Chrome 7.0.517.44 install, I appear to be identifiable by my user agent (1 in 182,518), brow…

When I run it twice in a row, why am I still unique?

Re: Race Is On to 'Fingerprint' Phones, PCs

#34
(throw away account...)

Full disclosure: I wrote one of these systems (AMA)

1. You'd probably be surprised what we can figure out from this. You'd also be surprised that there isn't much you can do to stop it from happening b/c we've been able to find ways to get information that is actually outside the browser.

2. You'd probably be surprised to see how embedded this is already. I'm guessing most people have had their browser fingerprinted at least once...for some reason. Knowing who used the services I wrote, I can tell you that they are everywhere...and given that I know our competitors also have this technology and who they work with...well...

3. There are legitimate uses to this tech besides spam. Its just that the money is in spam. I'm near 100% certain that most people will use this for spam in the next year or two.

Re: Race Is On to 'Fingerprint' Phones, PCs

#35

I foresee a future where the Adblock crowd runs a plugin that randomizes the data returned by browsers. It wouldn't take many variations in user agent strings, reported browser plugins, and system fonts to give you a quasi-anonymous footprint each time you visit a website.

or a completely identical infoblock - anonymity of the crowd

Surely by labelling yourself with this identical info block you're marking yourself as a type of person?

Re: Race Is On to 'Fingerprint' Phones, PCs

#36
post #2

Based on this article you can "fingerprint" a computer using the following combination of attributes: - Precise timestamp - Monitor size - User agent - Browser plugins - and fonts (!) Really?? I use several browsers, and switch out a few external displays for my laptop. Plugins come and go with the browser version. My system time is synced to a timeserver (as I imagine are many other computers) but sometimes not. Bas…

-Your browser fingerprint appears to be unique among the 1,279,589 tested so far.

Guess using Opera helps with my uniqueness! >_<

Re: Race Is On to 'Fingerprint' Phones, PCs

#37
post #32
post #26

Earlier quoted context omitted.

The thing about Panopticlick is that the two most "accurately" identifying methods aren't stable fingerprints. As soon as you install an update to one of your plugins (the constant Adobe updates come to mind), your fingerprint is altered. Similar with the font list; programs seem to be installing new fonts on my system all the time, which makes that fingerprint unstable as well.

Yes. If you wanted to get serious, you should deal with unstable characteristics. Perhaps with Bayesian filtering or something? And maybe adding some outside information, like when the new flash plugin is released; and tracking if a user is likely to upgrade or not. If you have a working solution for unstable characteristics, you can also add more more characteristics, than they do at the moment. My scree1050x3360x24

Oops, I wanted to write: My resolution and colour depth alone (1050x3360x24) identifies me for 18 bits at that site.

Re: Race Is On to 'Fingerprint' Phones, PCs

#38

I foresee a future where the Adblock crowd runs a plugin that randomizes the data returned by browsers. It wouldn't take many variations in user agent strings, reported browser plugins, and system fonts to give you a quasi-anonymous footprint each time you visit a website.

A couple of years ago, I set up privoxy to rotate my user agent string periodically, usually once an hour (once I even changed it once per request). As fun as this was, even when running adblock and noscript and flashblock, it was obviously not very effective.

This kind of fingerprinting does not bode well for TOR users. What is required is an intermediate proxy that modifies the out-bound browser traffic to delete or randomly modify these highly-unique sets of info (font sets, plugin sets, etc.) presented by the browser.

I'm still amazed at how much info flash, java, and javascript can glean about a system. I'm curious... is it possible to get the username or file/directory names readable by that user from the browser?

Re: Race Is On to 'Fingerprint' Phones, PCs

#39
post #27

The question we should all be asking is: why on Earth do browsers transmit all of this information to web servers in the first place? A few details, window size for example, might have a legitimate purpose and could at least be requested by the web server and provided optionally. However, this sort of fingerprinting technique is pretty obvious to anyone who's ever stuck an analyser on their system and looked at what…

Really? I can see a good use case for the ones that are described at Panopticlick. Things like http_accept, plugin details and fonts are necessary if you want to use the capabilities of the client - you need to know what they have. The time zone, screen size and (to a certain extent) user-agent let you customise the content you serve in an appropriate way. Providing it "optionally" doesn't seem like a solution. If yo…

Things like http_accept, plugin details and fonts are necessary if you want to use the capabilities of the client - you need to know what they have.

I disagree rather strongly with sending things like user agent strings, plugins and fonts by default. There should be no need for a web site to know anything about either. Indeed, customising content to that degree based on specifics of the client's software identity rather than providing adaptive content seems somewhat anti-WWW to me.

Moreover, given the number of plugins with security issues widely available for some browsers, sending a list of installed plugins and versions with every HTTP request is practically begging to get malware back if you're not 100% patched up (and even if you are, if you're unlucky with a 0-day exploit).

Let me put it this way: most web sites that I've encountered actively modifying their content based on specific user agents have been places like banks, and usually the reason I know that they were doing this is because they got it wrong and consequently refused to serve perfectly good content to a browser perfectly capable of rendering it as intended because of concerns about some security flaws in browsers from another era. I'm not sure I have ever come across a web site that actively modifies the content it provides based on the browser plugins or fonts on the client system.

Providing it "optionally" doesn't seem like a solution. If you were prompted every time then most people would turn it on anyway, and any ad network site would obviously ask for everything that it could possible get.

On the contrary. I think people would very quickly tire of visiting sites whose ad networks caused such problems, and the ad networks would have to give up doing it or quality sites would drop them. Indeed, the only common uses for this kind of information today seem to be supporting user tracking or deployment of targeted malware from compromised sites. Providing the detailed information only to sites that explicitly request it and possibly only if the user's security settings permit would make life more difficult for both groups, and I have no problem with this outcome.

Re: Race Is On to 'Fingerprint' Phones, PCs

#40

The question we should all be asking is: why on Earth do browsers transmit all of this information to web servers in the first place? A few details, window size for example, might have a legitimate purpose and could at least be requested by the web server and provided optionally. However, this sort of fingerprinting technique is pretty obvious to anyone who's ever stuck an analyser on their system and looked at what…

Because not transmitting that information doesn't get you much. You only need 30 bits of identifying information to track a billion users. With basic stuff like IP address, time zone, screen size, user agent, and supported plugins, you're pretty much there. The web server asking the browser "do you support X?" increases latency and doesn't help anonymity. Bad web servers could just ask, "Do you support X, Y, Z, and w…

You only need 30 bits of identifying information to track a billion users.

You need 30 unique bits of information.

Given that there are only a handful of common screen resolutions, for example, they are unlikely to represent more than a few bits in most cases, and if you provided current size of the viewable area in the browser instead (a more useful measurement anyway) then in many cases this would change over time. If you further provide this information only on explicit request, and potentially lock it down to only the host site rather than third party content, then it is of almost no use to anyone with unwelcome intentions.

Post reply on HN