-
Notifications
You must be signed in to change notification settings - Fork 971
Feature request: expose the options to disable/enable Tor #14603
Comments
Thinks this will be fixed by #12989. cc: @riastradh-brave |
@srirambv Thanks! A temporary fix for me was to kill the tor daemon in the CLI
|
Can i disable tor? Kill a process isn't the best way! |
@johnpwarren Wouldn't lazy-loading Tor fix this? I.e., rather than add a new preference, we don't start the Tor process until/unless user invokes a Tor private tab. |
#12989 won't fix this -- it will just provide another way to reach the Tor network if the default one doesn't work. Deferring and/or configuring tor startup is under discussion. |
@davidtemkin I would assume that would be correct. Still, having detailed control over Tor would be more desirable. My experience was actually coming into the office in the morning and learning about Tor traffic from my workstation from the aforementioned CyberDefense guys. I could replicate it by killing the Tor process, stopping and starting Brave. I haven't checked yet to see if Brave stops the process on exit yet. |
Also, it's probably not a good idea for browser updates to happen over Tor (I am now not the only person in the office who has ticked off the CyberDefense guys [ tor traffic laptop-updates.brave.com]). |
Removing this from the milestone since #14617 will disable Tor until the user explicitly opens a Tor tab. |
Closing in favor of brave/brave-browser#454 |
Description
I've run into the problem that on some networks I use Tor is banned, but there is no easy configuration to turn off Tor. There is an error popup that shows up when trying to open a private tab that gives an option to turn off Tor but this really seems like it belongs in the preferences.
Stretch goal on this would be to enable Tor in shields so you can have site by site control.
Steps to Reproduce
Brave Version
about:brave info:
Reproducible on current live release:
Yes
Additional Information
Tor is a great feature, I'd just like more control over it.
The text was updated successfully, but these errors were encountered: