Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

Fingerprinting protection on by default in Tor private tabs #13735

Closed
riastradh-brave opened this issue Apr 5, 2018 · 2 comments
Closed

Fingerprinting protection on by default in Tor private tabs #13735

riastradh-brave opened this issue Apr 5, 2018 · 2 comments
Labels
feature/tor open-in-brave-core

Comments

@riastradh-brave
Copy link
Contributor

riastradh-brave commented Apr 5, 2018 •
edited
Loading

Fingerprinting protection should be enabled by default in Tor private tabs. It may be already, in which case we can close this issue immediately; just need a reminder to check while I'm flushing old notes from the wiki page.

Old notes also suggest disabling JavaScript in Tor private tabs; not sure whether we want to do that but we should revisit rather than drop it on the floor.
@tildelowengrimm tildelowengrimm added this to the 0.24.x (Nightly Channel) milestone Apr 17, 2018
@diracdeltas diracdeltas removed this from the 0.24.x (Nightly Channel) milestone Apr 18, 2018
@diracdeltas diracdeltas mentioned this issue May 10, 2018
Closed
@srirambv
Copy link
Collaborator

srirambv commented Jul 9, 2018

https://jsfiddle.net/bkf50r8v/13/ this blocks all 3 FP methods by default on Tor tab. Disable shields only blocks WebRTC but allows Canvas and WebGL.
image

@bsclifton bsclifton mentioned this issue Sep 7, 2018
Open
@bsclifton
Copy link
Member

Closing in favor of brave/brave-browser#1011

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
feature/tor open-in-brave-core
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@diracdeltas @tildelowengrimm @bsclifton @srirambv @riastradh-brave