Open dave-circle opened 3 months ago
Hi.
Yes, this is expected as Safari has fingerprinting protections. However, FingerprintJS has an implementation that evades this. https://fingerprint.com/blog/bypassing-safari-17-audio-fingerprinting-protection/
I also have a repo that lists fingerprinting protections by browser, and any issues with those protections. I currently have this listed in that repo if anyone finds it useful. https://github.com/Joe12387/browser-fingerprinting-resistance-research
Thanks!
I'll keep this open as a possible enhancement for the future. I don't own a Mac and looks like the new Safaris don't run on Win11
The issue is also present on IOS as well with Safari in private browsing mode.
Hi, are we able to bypass safari anti-fingerprinting which is where canvas-fingerprinting is not working if we turned on safari fingerprinting protection or can you guys share the resource for bypassing the safari anti-fingerprinting for canvas .
Not really sure if or how the canvas fingerprinting could be bypassed, unless you disable it for safari altogether, and doing that then removes that capability from the non-private mode too. Or, you could detect when safari is in private mode and disable the canvas fingerprint then, but still the non-private and private mode fingerprints will not match, and the safari private mode fingerprint would be very common among other safari private fingerprints.
While testing in incognito, I noticed that the finger print that was generated was different. Is this expected? I used the JSON compare tool that was linked on the site. The difference was in the audio.sampleHash values between the two separate incognito windows.
Safari Version 17.3 macOS Sanoma