Open
Bug 1325874
Opened 8 years ago
Updated 2 years ago
Consider seperating page content history for userContextId
Categories
(Core :: DOM: Security, defect, P3)
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox57 | --- | fix-optional |
People
(Reporter: jkt, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
(Whiteboard: [fingerprinting][fp-triaged][domsecurity-backlog2][userContextId])
We should consider if we also want to isolate page history for in-content itself.
For example visited links across containers shouldn't leak history information which could be exploted via the various privacy leak techniques.
STR:
1. Visit google.com
2. Search for 'This is a Test'
3. Click the first result
4. Open a 'Personal' tab
5. Visit google.com
6. Search for 'This is a Test'
7. Notice the first result has been visited.
|
||
Updated•8 years ago
|
Priority: -- → P3
Whiteboard: [fingerprinting][domsecurity-backlog2][userContextId]
|
||
Updated•8 years ago
|
Blocks: uplift_tor_fingerprinting
|
||
Comment 1•7 years ago
|
||
Bulk change per https://bugzilla.mozilla.org/show_bug.cgi?id=1401020
status-firefox57:
--- → fix-optional
|
||
Updated•6 years ago
|
No longer blocks: uplift_tor_fingerprinting
Whiteboard: [fingerprinting][domsecurity-backlog2][userContextId] → [fingerprinting][fp-triaged][domsecurity-backlog2][userContextId]
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•