Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Browser Tor Browser
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 881
    • Issues 881
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 17
    • Merge requests 17
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Applications
  • Tor BrowserTor Browser
  • Issues
  • #8934
Closed
Open
Issue created May 22, 2013 by Trac@tracbot

ExitNodes 1 being ignored

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

Trac:
Username: thmprrr

Assignee
Assign to
Time tracking