[quote]
Despite browsing incognito, blocking advertisements, or hiding your tracks, some websites monitor and track your every move online using a new web-tracking technique called Audio Fingerprinting.
This new fingerprinting technique can be utilized by technology and marketing companies to deliver targeted advertisements as well as by law enforcement to unmask VPN or Anonymous users, without even decrypting the traffic.
Researchers at Princeton University have conducted a massive privacy survey and discovered that Google, through its multiple domains, is tracking users on nearly 80 percent of all Top 1 Million Domains using the variety of tracking and identification techniques.[/quote]
I’ve found the same here - so clearing cookies and cache (or going incognito) won’t help.
I’m pretty sure that combined with an IP, they could reasonably determine users cross browsers too.
I think they might be coming up with these new techniques because Flash is about to be killed off - flash was great to track users previously (even cross browser).
Except, unfortunately, the act of using Safari automatically helps with fingerprinting you, since Safari is between 10-20% market share (depending on the site you’re measuring).
I assume Tor Browser treats audio the same way it treats canvas, right?
This is mine on Firefox nightly 57.0a1 (2017-08-17).
Fingerprint using DynamicsCompressor (sum of buffer values):
35.74996018782258
Fingerprint using DynamicsCompressor (hash of full buffer):
158e8189a3551fe4f2e564ac377b0f1e588a1ab3
They very seem close in number, though I’m not really sure what the metric is. I usually use uBlock and noscript which I think should prevent this, though they’ve been broken in nightly for the past two days.
an AudioContext fingerprint is a property of your machine’s audio stack itself
It seems like the operating system and audio drivers play a role in the fingerprint. I think the AudioContext properties are set by the user/browser, so differences there will be apparent, but measuring the underlying raw audio buffers is a lot more subtle and machine dependant.
EDIT: but here TOR should still be blocking Canvas/AudioContext, the audio stack doesn’t effect that