Bypassing Safari 17's advanced audio fingerprinting protection

Post by tagCollector » Sun, Mar 10, 2024, 4:00 AM UTC

exabrial wrote: post #108

I'm really ready to just be "that guy" that browses with JS disabled.

Post by lapcat » Sun, Mar 10, 2024, 4:02 AM UTC

saagarjha wrote: post #105

I feel like these days (especially given the recent focus on side channel attacks) it is basically a given that adding uniform noise to something that leaks data does not work, because you can always take more samples and remove the noise. Why did Safari add this? I understand that needing more samples is definitely an annoyance to fingerprinting efforts, but as this post shows it's basically always surmountable in s…

Post by tagCollector » Sun, Mar 10, 2024, 4:04 AM UTC

Crespyl wrote: post #22

fbdab103 wrote: post #17

Earlier quoted context omitted.

I think that is correct, but it still seems like an amount of leakage that could be further correlated with other another trick. There was previously a site which could indicate how globally unique your environment was (some combination of screen size, user-agent, fonts?, etc). Locking down to a specific hardware+browser configuration probably does a lot to remove anonymity.

You may be thinking of https://www.amiunique.org/fingerprint

Post by tagCollector » Sun, Mar 10, 2024, 4:10 AM UTC

Borealid wrote: post #73

sshumaker wrote: post #70

It seems like rather than adding a random amount to each sample (which lets them compute a mean by recreating the same audio and extracting out the differences), Safari could instead add randomness that is based on a key that rotates every hour. (Function of audio sample and key, so the noise would be the same in a given session, but useless for tracking an hour later).

If you averaged together ten such samples, you'd get something that approaches the true values from the device. The more samples you have, the closer it would get. Fixing this would require removing the information leak entirely, not just masking it under a layer of random deviations.

Post by dannyw » Sun, Mar 10, 2024, 4:31 AM UTC

spookie wrote: post #97

nox101 wrote: post #83

Earlier quoted context omitted.

I'm the opposite. I think website = sanboxed, native = pownage so whenever I can use a website version I often prefer it over a native app. I use photopea all the time now. it's available on every machine, even machines I don't have permission to install software on

You can sandbox native apps too. Hell, even run them in an airgapped virtual machine. I wouldn't trust a browser sandbox all that much given the high interest in subverting it.