[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-talk] using locally installed Tor in TBB
> in 3.6.3 TBB linux amd-64 i changed the port to 9050
> my local install of Tor is on the jessie alpha channel
> when i close & restart TBB i get:
> Something Went Wrong!
> Tor is not working in this browser.
This happens because of missing Tor ControlPort access.
There are no instructions for how to use TBB with system Tor. But it is
Maybe you can add this to torproject.org's wiki?
## Deactivate tor-launcher,
## a Vidalia replacement as browser extension,
## to prevent running Tor over Tor.
## The following TOR_SOCKS_HOST and TOR_SOCKS_PORT variables
## do not work flawlessly, due to an upstream bug in Tor Button:
## "TOR_SOCKS_HOST, TOR_SOCKS_PORT regression"
What should work quite well is using env var "export TOR_SKIP_LAUNCH=1"
combined with rinetd, redirecting traffic from TBB's ports 9150 and 9151
to 127.0.0.1 with a config like this:
127.0.0.1 9150 127.0.0.1 9050
127.0.0.1 9151 127.0.0.1 9051
You also need some form of ControlPort authentication.
tor --hash-password password
See Tor manual HashedControlPassword.
to /etc/tor/torrc and reload (/restart?) Tor.
> this is repeatable behaviour opening/closing TBB
> some Tor log looks ok though and apart from logs it obviously does work
> on 9050
> [NOTICE] Bootstrapped 85%: Finishing handshake with first hop.
> [NOTICE] Bootstrapped 90%: Establishing a Tor circuit.
> [NOTICE] Tor has successfully opened a circuit. Looks like client
> functionality is working.
> [NOTICE] Bootstrapped 100%: Done.
> [NOTICE] New control connection opened.
> as an aside would it be discouraged to use the alpha in TBB and not the
> bundled Tor version 0.2.4.22 (git-345e00dc68a052fe) ?
> pros/cons either way ?
- easier to keep your entry guards longer
- more difficult to set up
tor-talk mailing list - tor-talk@xxxxxxxxxxxxxxxxxxxx
To unsubscribe or change other settings go to