[tor-bugs] #3143 [Tor Client]: Cannot avoid rogue ExitNodes

[Tor Bug Tracker & Wiki]

#3143: Cannot avoid rogue ExitNodes
------------------------+---------------------------------------------------
 Reporter:  aa138346    |          Owner:                     
     Type:  defect      |         Status:  new                
 Priority:  critical    |      Milestone:                     
Component:  Tor Client  |        Version:  Tor: 0.2.2.25-alpha
 Keywords:  hijack      |         Parent:                     
   Points:              |   Actualpoints:                     
------------------------+---------------------------------------------------
 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.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/3143>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online