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

Re: [tor-bugs] #4994 [Tor Client]: Be willing to use microdescs even if one bridge runs 0.2.2

#4994: Be willing to use microdescs even if one bridge runs 0.2.2
------------------------------+---------------------------------------------
 Reporter:  arma              |          Owner:                    
     Type:  enhancement       |         Status:  needs_revision    
 Priority:  normal            |      Milestone:  Tor: 0.2.4.x-final
Component:  Tor Client        |        Version:                    
 Keywords:  microdescriptors  |         Parent:                    
   Points:                    |   Actualpoints:                    
------------------------------+---------------------------------------------
Changes (by nickm):

  * status:  needs_review => needs_revision


Comment:

 There's going to be a few interesting problem here, unless there's
 something in your patch that I missed.

 When a client starts up, which consensus will it download?  It doesn't
 know its nodes' versions yet, so it doesn't know if any of its bridges
 have microdescriptors or not.  It won't know until it gets some consensus
 and sees the "p" lines there.  But if it asks for the wrong one, it needs
 to turn around and download the other.

 Oh hey, I don't think that non-microdesc bridges will serve microdesc-
 consensuses, right?  So we'd better restrict those downloads too.  Also,
 if we try to download the microdesc consensus from our bridges and fail,
 we'll never actually learn their versions in any way that node_t will see,
 so we'll never learn that they don't support microdescs.

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