-
Notifications
You must be signed in to change notification settings - Fork 448
WebGL fingerprint protection #478
Comments
Fingerprint protection is currently looking more into canvas FP. For WebGL FP, we have to build a list of all possible WebGL functions which can be used to generate a fingerprint. Another way of handling this FP is by disabling WebGL completely when FPP is on, or spoof the video card info. |
This is reproducible in 1.6 as well. 🤕 |
Canvas and WebRTC were the only two things blocked on current release version. |
@jhreis - Ok cool. This does not block 1.7. I'll tag the issues that are blocking from the security standpoint accordingly. For now, I'm filing all security/privacy issues that I run into, let me know if you want me to hold off on filing the low-pri issues for now? |
This is addressed in 1.19. |
Closing and moving to 1.20 for formal QA verification |
Verification passed on iPhone XR with iOS 13.5 running 1.20(20.08.13.15)
Verification passed on iPhone 7+ with iOS 14 running 1.20(20.08.13.15)
Verification passed on iPhone 6 with iOS 12.4.7 running 1.20(20.08.13.15)
Verification passed on iPad Pro with iOS 13. running 1.20(20.08.13.15)
Verification passed on iPad Pro with iOS 13.5 running 1.20(20.08.13.15)
|
Description:
WebGL fingerprinting works with fingerprinting protection turned on
Steps to Reproduce
Actual result:
WebGL fingerprinting works
Expected result:
Should not work
Reproduces how often: [Easily reproduced, Intermittent Issue]
Always
Brave Version:
Development version (60a82d3)
Device details:
Simulator (iPhone XS - iOS 12.1)
The text was updated successfully, but these errors were encountered: