[tor-bugs] #3296 [Tor Client]: Exitnode that can't handle a predicted port -> endless circuit creation

Tor Bug Tracker & Wiki torproject-admin at torproject.org
Thu May 26 22:04:12 UTC 2011


#3296: Exitnode that can't handle a predicted port -> endless circuit creation
------------------------+---------------------------------------------------
 Reporter:  arma        |          Owner:                    
     Type:  defect      |         Status:  new               
 Priority:  major       |      Milestone:  Tor: 0.2.2.x-final
Component:  Tor Client  |        Version:                    
 Keywords:              |         Parent:                    
   Points:              |   Actualpoints:                    
------------------------+---------------------------------------------------
 I set "exitnode cherrybomb" on my maint-0.2.2:

 {{{
 May 26 17:52:38.802 [notice] All routers are down or won't exit --
 choosing a doomed exit at random.
 May 26 17:52:39.493 [notice] All routers are down or won't exit --
 choosing a doomed exit at random.
 May 26 17:52:39.689 [notice] All routers are down or won't exit --
 choosing a doomed exit at random.
 May 26 17:52:39.810 [notice] All routers are down or won't exit --
 choosing a doomed exit at random.
 ...
 }}}

 Looking in more detail at the logs, I see
 {{{
 May 26 17:52:17.061 [debug] circuit_remove_handled_ports(): Port 5222 is
 not handled.
 }}}

 My pidgin wanted to talk AIM, but my exitnode doesn't allow 5222.

 A 'getinfo circuit-status' on the control port showed scores of circuits
 all ending at cherrybomb.

 Tor should ignore predicted ports for destinations its configured exit
 nodes can't handle, rather than making an infinite pile of circuits that
 wouldn't be able to handle the requests anyway.

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


More information about the tor-bugs mailing list