Opened 6 years ago

Closed 4 years ago

#8934 closed defect (worksforme)

ExitNodes 1 being ignored

Reported by: thmprrr Owned by: tbb-team
Priority: Medium Milestone: TorBrowserBundle 2.3.x-stable
Component: Applications/Tor Browser Version: Tor: 0.2.3.25
Severity: Keywords: exitnodes, needs-triage
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Using Tor Browser Bundle 2.3.25-6 and 2.3.25-8 (Windows)

Have placed the following settings in the torrc file:

ExitNodes {SE}
StrictNodes 1

Older versions of Tor would simply not connect (and give me error messages in the Vidalia message log) when it could not find a suitable exit node. However 2.3.25-6 has given me non-SE exit nodes frequently. I used it as an excuse to upgrade to 2.3.25-8 but am experiencing the exact same thing.

I had no problem with previous versions (sorry, already deleted older bundle so cannot verify the older version that used to work) where it would simply refuse to connect - at least I would know that a suitable exit node could not be found. But ignoring this setting seems dangerous. Any ideas?

Using Tor Browser Bundle 2.3.25-8
Vidalia 0.2.21
Tor 0.2.3.25 (git-17c24b3118224d65)
Qt 4.8.1

Child Tickets

Change History (6)

comment:2 Changed 6 years ago by arma

I wonder if the bundles have the geoip file set up correctly?

(I wonder if Tor should break more obviously if you set a country code in one of the torrc options, but it can't find a geoip file. (Or maybe it does already?))

comment:3 Changed 5 years ago by nickm

Component: TorTor bundles/installation
Owner: set to erinn

comment:4 Changed 4 years ago by erinn

Keywords: needs-triage added

comment:5 Changed 4 years ago by erinn

Component: Tor bundles/installationTor Browser
Owner: changed from erinn to tbb-team

comment:6 Changed 4 years ago by arma

Resolution: worksforme
Status: newclosed

I suggest closing this one, since any number of fixes and re-packagings have happened since the bug report.

Please open a new ticket if there is still an issue here.

Note: See TracTickets for help on using tickets.