-
Notifications
You must be signed in to change notification settings - Fork 974
Unique Device ID's #1883
Comments
Duping to #260 |
Reopened for Unique Device ID of WebRTC Media Device Enumeration. Should we remove it? cc: @diracdeltas |
We can leave this open. Unique device IDs themselves are not a problem, but Brave does not uniquely set them between different browsing sessions, so they can be used for cross-session tracking. cf https://w3c.github.io/mediacapture-main/#def-constraint-deviceId |
Test page (try opening in different sessions in brave vs chrome): https://jsfiddle.net/22e4yfvg/ |
Confirmed, they are shared across sessions. |
@bridiver are you taking this? |
ping on this |
yea, I can look at it. We also need to clear the device id when clearing other session data |
thx |
this seems to have been automatically fixed in the latest libchromium update. the device ids are not shared between sessions anymore, and they are reset on restart. i'll keep this open to track clearing the device ids when other session data is manually cleared |
closing this and opening follow-up so QA knows this was actually fixed in 0.12.2. #4157 test plan:
|
please remove this
WebRTC Media Device Enumeration
Unique Device ID's
http://www.browserleaks.com/webrtc
The text was updated successfully, but these errors were encountered: