Re:How We Bypassed Safari 17's Advanced Audio Fingerprinting...
by kmlx on Saturday March 09, 2024 @07:14PM
(#39655677)
> Someone else with the same browser, OS, and laptop model would have the same fingerprint.
the collision rate of their ids is stated to be 0.05%
what they do is basically collect a lot of signals from the browser (audio processing stuff being only a part of it) and then compute an id on the server.
Re:How We Bypassed Safari 17's Advanced Audio Fingerprinting...
by spookie on Saturday March 09, 2024 @07:36PM
(#39655799)
Still, parent does state a pretty big concern when looking at this from a higher vantage point.
These practices and their repercussions aren't self contained.
Re:How We Bypassed Safari 17's Advanced Audio Fingerprinting...
by azmodeus on Saturday March 09, 2024 @06:33PM
(#39655498)
Browser, OS, laptop joined with IP looks like a pretty good ID
Re:How We Bypassed Safari 17's Advanced Audio Fingerprinting...
by ryan-c on Saturday March 09, 2024 @06:52PM
(#39655591)
IP is a pretty good ID...
Re:How We Bypassed Safari 17's Advanced Audio Fingerprinting...
by azinman2 on Saturday March 09, 2024 @07:49PM
(#39655863)
Not if you’re behind something NAT’d, which is especially true on mobile.
I don't think that's what stockhorn said. stockhorn said it can only identify a what browser and OS and laptop model you're using. Someone else with the same browser, OS, and laptop model would have the same fingerprint. So audio fingerprinting couldn't precisely recognize you again when you come back again.