Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #3143

Closed (moved)
Open
Opened May 11, 2011 by Trac@tracbot

Cannot avoid rogue ExitNodes

I am trying to avoid certain Nodes and ExitNodes which seem to be hijacking traffic and forcing an exit.

This really raises my suspicions.

For example, I have noticed that the node:

66.249.9.107 (resolves to selectresponse.com.9.249.66.in-addr.arpa.)

will force itself to be an exit node, despite my attempts to ban it in my configuration file. I have tried using the ExcludeExitNodes and even ExcludeNodes directives, reloading the configuration of course.

I do not understand the way that circuits are built well enough to know if this is something that the client has any control over, both at the time of building the circuit or and after the circuit is built.

I have had noticed this phenomenon with a handful of other ExitNodes as well, and it obviously opens all sorts of problems if these are bad actors.

I have verified this behavior with tor clients (stable and unstable) up to version 0.2.2.25 in both linux and windows.

Trac:
Username: aa138346

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#3143