Use an OS-chosen port number for tor socks proxy #649
Labels
bug
feature/tor
needs-investigation
A bug not 100% confirmed/fixed
OS/Desktop
priority/P4
Planned work. We expect to get to it "soon".
QA Pass-Linux
QA Pass-macOS
QA Pass-Win64
QA/Yes
release-notes/include
Milestone
Currently, in browser-laptop, we use port 9250, 9260, 9270, 9280, or 9290 for the tor socks proxy, depending on the release channel. This allows a standard release of Brave to coexist with a beta release to coexist with a local development build, but not more than one of each kind at a time, and if anything happens to be using the port number when Brave starts, it just fails. We should let the tor daemon ask the OS to choose an unused port number and use that instead.
This requires an extra step from what we currently do in browser-laptop. Specifically, currently, we:
socks5://127.0.0.1:9250
.--socksport 9250
.Instead, we should:
--socksport 0
.GETINFO net/listeners/socks
.The text was updated successfully, but these errors were encountered: