[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-bugs] #3599 [Tor Client]: Microdescriptor policy comparison handles "unspec" incorrectly

#3599: Microdescriptor policy comparison handles "unspec" incorrectly
------------------------+---------------------------------------------------
 Reporter:  nickm       |          Owner:                    
     Type:  defect      |         Status:  new               
 Priority:  major       |      Milestone:  Tor: 0.2.3.x-final
Component:  Tor Client  |        Version:                    
 Keywords:              |         Parent:                    
   Points:              |   Actualpoints:                    
------------------------+---------------------------------------------------
 If you start a microdesc client and wait a while, you'll start to see lots
 of "No exits can handle address [scrubbed]" messages.

 This happens because the uint32_t value 0 is used in address policy
 comparison code to mean both the address 0.0.0.0 and "no address known".
 0.0.0.0 is blocked by everybody, so compare_tor_addr_to_short_policy()
 says "reject" for everybody.

 I'm not currently quite sure why it take so long for this to trigger.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/3599>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs