Re: [tor-bugs] #6537 [Tor Client]: Possible timing side-channel in router selection

["Tor Bug Tracker & Wiki" <torproject-admin@xxxxxxxxxxxxxx>]

#6537: Possible timing side-channel in router selection
---------------------------+------------------------------------------------
    Reporter:  nickm       |       Owner:                    
        Type:  defect      |      Status:  closed            
    Priority:  major       |   Milestone:  Tor: 0.2.2.x-final
   Component:  Tor Client  |     Version:                    
  Resolution:  fixed       |    Keywords:                    
      Parent:              |      Points:                    
Actualpoints:              |  
---------------------------+------------------------------------------------

Comment(by cypherpunks):

 Replying to [comment:5 cypherpunks]:
 > the_nodelist->nodes will be sorted by calling of
 nodelist_set_consensus() if consensus was loaded first. it should happen
 for most usage scenarios.
 >
 > So we should assume smartlists determinately sorted.

 It's true only if client used that firstly loaded consensus.
 the_nodelist->nodes will never be resorted for next consensuses. Depends
 client uptime and relays statuses it could be not so obvious what order of
 the_nodelist->nodes in result.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/6537#comment:6>
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