Open
Bug 1329996
(uplift_tor_fingerprinting)
Opened 8 years ago
Updated 13 days ago
[META] Tor Uplift: Fingerprinting Resistance
Categories
(Core :: DOM: Security, task, P2)
Core
DOM: Security
Tracking
()
NEW
mozilla54
People
(Reporter: ethan, Unassigned, Mentored)
References
(Depends on 37 open bugs, Blocks 2 open bugs)
Details
(Keywords: meta, Whiteboard: [tor][fingerprinting][domsecurity-meta][fp-triaged])
As part of the Tor uplift project, we are going to implement anti-fingerprinting protection [1] in Firefox.
This bug is used as the meta bug of all anti-fingerprinting features.
Reference:
[1] Cross-Origin Fingerprinting Unlinkability
https://www.torproject.org/projects/torbrowser/design/#fingerprinting-linkability
Reporter | ||
Updated•8 years ago
|
Alias: AntiFingerprinting
Assignee: nobody → ettseng
Blocks: meta_tor
Priority: -- → P2
Whiteboard: [tor][fingerprinting][domsecurity-meta]
Target Milestone: --- → mozilla54
Reporter | ||
Updated•8 years ago
|
Comment 1•8 years ago
|
||
Fingerprinting defenses work best when they are used together. Therefore an idea we have proposed is to make all anti-fingerprinting features active when the pref "privacy.resistFingerprinting" = true. That will make it easier for users to activate all anti-fingerprinting features at once, and also will give a simple definition of what is included in Firefox's fingerprinting resistance so that we can measure our progress using tools such as https://panopticlick.eff.org/. Also, Tor Browser will enable this pref.
Updated•8 years ago
|
Blocks: AntiFingerprintingMeasurement
Comment 2•7 years ago
|
||
Bug 1077986 could also be added
Updated•7 years ago
|
Depends on: letterboxing
Reporter | ||
Updated•7 years ago
|
Whiteboard: [tor][fingerprinting][domsecurity-meta] → [tor][fingerprinting][domsecurity-meta][fp-triaged]
Updated•7 years ago
|
Assignee: ethantseng → nobody
Updated•7 years ago
|
Depends on: finegrained-rfp
Comment 4•6 years ago
|
||
Recent research suggests the work on anti-fingerprinting being done here matters a lot : https://freedom-to-tinker.com/2018/06/29/against-privacy-defeatism-why-browsers-can-still-stop-fingerprinting/
Thanks for the work already done here by the Firefox and Tor teams and looking forward to new improvements as well :-)
Reporter | ||
Updated•6 years ago
|
Whiteboard: [tor][fingerprinting][domsecurity-meta][fp-triaged] → [tor][fingerprinting][domsecurity-meta]
Reporter | ||
Comment 5•6 years ago
|
||
From now on, this meta bug is used to track anti-fingerprinting bugs which will be used by Tor Browser. The purpose is to help us narrow down the scope of the Tor Uplift project, and track its progress more easily.
If a bug is a fingerprinting issue in general, but not necessary to fix for Tor, we'll simply mark it as [fingerprinting] in Whiteboard and not block this meta bug.
Alias: AntiFingerprinting → uplift_tor_fingerprinting
Summary: [META] Support anti-fingerprinting protection → [META] Tor Uplift: Fingerprinting Resistance
Updated•6 years ago
|
No longer depends on: finegrained-rfp
Updated•6 years ago
|
No longer blocks: AntiFingerprintingMeasurement
Updated•6 years ago
|
Assignee: nobody → ettseng
Whiteboard: [tor][fingerprinting][domsecurity-meta] → [tor][fingerprinting][domsecurity-meta][fp-triaged]
Updated•6 years ago
|
Depends on: remove-native-theming
Comment 7•4 years ago
|
||
Mozilla should follow Apple's attitude and disable some Web APIs by default: https://www.zdnet.com/article/apple-declined-to-implement-16-web-apis-in-safari-due-to-privacy-concerns/
The more features have to be disabled by Fingerprinting Resistance, it becomes less effective and users have a risk of standing out.
Thanks for listening.
Reporter | ||
Updated•2 years ago
|
Assignee: ettseng → nobody
Updated•2 years ago
|
Severity: normal → S3
Updated•1 year ago
|
See Also: → finegrained-rfp
Updated•1 month ago
|
Type: defect → task
You need to log in
before you can comment on or make changes to this bug.
Description
•