Open
Bug 1152448
Opened 10 years ago
Updated 2 years ago
"Forget About This Site" does not forget site's enumerateDevices Ids
Categories
(Core :: WebRTC: Audio/Video, defect, P3)
Core
WebRTC: Audio/Video
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox40 | --- | affected |
backlog | webrtc/webaudio+ |
People
(Reporter: jib, Unassigned, NeedInfo)
References
Details
(Keywords: privacy, Whiteboard: [fingerprinting][fp-triaged])
Unlike for cookies, selecting a site in the History panel and choosing "Forget About this Site", does not clear enumerateDevices's deviceIds for that site.
As such, someone may expect the site not to be able to identify them after having taken this action.
Need to add a SanitizeOriginKey(origin) method for this.
Updated•10 years ago
|
backlog: --- → webRTC+
Rank: 25
Priority: -- → P2
Comment 1•7 years ago
|
||
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
Comment 2•7 years ago
|
||
Yeah, this is a great example for the sort of issue that bug 1422365 is supposed to fix.
Updated•6 years ago
|
Whiteboard: [fingerprinting] → [fingerprinting][fp-triaged]
Comment 3•6 years ago
|
||
If someone ends up doing this, it would be best to add a deleteByHost or deleteByPrincipal method that calls into the platform code here: https://searchfox.org/mozilla-central/rev/5117a4c4e29fcf80a627fecf899a62f117368abf/toolkit/components/cleardata/ClearDataService.js#265
Comment 4•4 years ago
|
||
johann, worksforme: I don't see a per site forget
anymore, it's just everything time based
- as shown here: https://support.mozilla.org/en-US/kb/forget-button-quickly-delete-your-browsing-history
- tested with and w/out LSNG
- closing the tab automatically means the current random device ids are dropped
The other one to consider is padlock>clear cookies and site data: that doesn't clear the id (i.e the tab stays open, clear, reload tab), but I don't know if that is in scope or in another issue somewhere
Flags: needinfo?(jhofmann)
Updated•3 years ago
|
Flags: needinfo?(jhofmann)
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•