I'd really like to see the browsers take on this practice. Safari, for example disables 3rd party cookies by default, but leaves open this huge hole via Flash.
I'd really like to see the browsers take on this practice. Safari, for example disables 3rd party cookies by default, but leaves open this huge hole via Flash.
Most of these tracking pixels are not flash anyway so blocking flash won't accomplish anything. Blocking Javascript will do something of course but some are only images so it will still be pointless and you'll still be tracked.
The reality IMHO is that it's better to be targeted by relevant ads than to see dating/scammy ads everywhere.
IMO it's better simply to add "rm -rf ~/.macromedia" to the list of shell commands that get executed upon every login -- or add the commmand as an entry on your personal crontab.
Windows users:
Documents and Settings/yourusername/Application Data/Macromedia/Flash Player/Shared Objects/your flash userid/
Documents and Settings/yourusername/Application Data/Macromedia/Flash Player/Macromedia.com/Support/Flashplayer/Sys/
Mac users: Places/yourusername/Library/Preferences/Macromedia/Flash Player/SharedObjects/your flash userid/
Places/yourusername/Library/Preferences/Macromedia/Flash Player/Macromedia.com/Support/Flashplayer/Sys/
Wow. I have flash cookies from over 700 sites.You can set it to clear your Flash cookies at the end or beginning of each session.
NoSciprt allows you to do that, so does Flashblock. I'm sure there are similar plugins and extensions for browsers other than Firefox (well, maybe not NoScript, it seems pretty unique).
Check your browser at http://panopticlick.eff.org/
Basically, using useragent, plugins, time zone, language, screen size, etc etc etc, you can fingerprint a user pretty reliably without using cookies.
Cookies are just an easy way to track users client side, but if there is an 'assault' on cookies, then people will just start relying more on server side tracking of users instead.
Disabling 3rd party cookies etc really achieves nothing.
Also, there's numerous methods you can use to store "cookies" in the browser these days, (localstorage api, http cookies, flash, cache etc)
If you really don't want to be tracked for some reason, disable javascript, clear out your user-agent, and use TOR.
fairly successful? eh.
One interesting thought: how much space would you need to pull this off? Chromium generates 12 KB of data which can gzip to 3KB, Firefox generates 5 KB of data which can gzip to a little over 1KB. Truncate-then-gzip could be used to keep perhaps 0 - 4 KB per person. Assume that your average user uses ~2KB. That's still rather a lot, when compared with what you can do with counters -- 8 bytes or so to store. If you wanted to keep your database under 2 TB, you could only handle a million people, not hundreds of millions. So it would really be a big distributed project to link identities as they evolve over time. I imagine that's one huge factor in using tracking cookies; it's lazy for scaling.
An interesting project might be to create a database having a table with the useragent hash as the primary key, and associate each identity in the user table to a number of these useragent hashes.
Those may be unique for your browser right now, but if you were to update your fonts or your plugins, that would generate a completely new user and all their information about you would be lost. Same as if you delete your cookies, but I bet it happens more frequently.
More than likely, only the browser version will change. For larger updates, would-be-broken plugins would disappear or see a newer version. It would be a ton of effort to track users this way, but I think it's within the realm of reason for those with enough incentive (NSA, maybe advertising companies)
Likely this could be done in a way that doesn't violate any terms of service or data disclosure promises. After all, pushing out "browser fingerprint 'abcd' and 'efgh' are the same person" isn't disclosing information that most people would realize they're trusting someone with.
I know that incognito mode is geared towards not leaving a trace on the user's computer rather than being anonymous to the server, but I guess I assumed that with the plugins disabled they wouldn't be visible to the server.
An alternative I'd like to see is a standard somewhat fixed small set of plugins and fonts.
AFAIK it's not very useful information and certainly removes one of the bigger unique factors.
User Agent provides quite a lot of identifying information; OS/OS version, browser version. Panopticlick breaks this down for you, one in every 186,062 data points they have has my User Agent. This provides 17.5 bits of identifying entropy (log2 of 186062).
They mention they have a total database size of 2,046,684, which requires 20.96 bits of identifying information. So to answer your question about how much identifying information you can get from Javascript, a lot.
You can then also get Flash Version, Time Zones, Browser Plugins, IP Address, Screen Info.
At which point the word BS comes to mind.
But just for grins, I repeated the test with a Chromebook fresh out of the box, and of course it's flagged "uniquely identifiable".
I'm not saying the underlying claim - browser characteristics can be used to track you - is bogus. I am saying that I think that site is intentionally exaggerating for effect. Or, more realistically, that while they can extract 20+ bits of info from those strings, the values in that 20+ bit domain are far from uniformly distributed.
But just because, I tried two more chromebooks (same model), both in guest mode, both stock configuration - and they're both flagged as "unique" too.
Maybe I'm just a victim of a really long update cycle of their database.
(Addendum: I went back with my original laptop, all cookies cleared, and it's indeed not considered unique any more. So maybe I really just saw some lag in updating their DB)
(Addendum 2: Just to clarify, I never doubted that you can be uniquely identified. But the "unique" part was wrong for my sample. )