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

Re: [tor-bugs] #2991 [Tor Client]: Confusing log messages when a DA starts using a new key

#2991: Confusing log messages when a DA starts using a new key
------------------------+---------------------------------------------------
 Reporter:  rransom     |          Owner:                  
     Type:  defect      |         Status:  new             
 Priority:  normal      |      Milestone:  Tor: unspecified
Component:  Tor Client  |        Version:                  
 Keywords:              |         Parent:                  
   Points:              |   Actualpoints:                  
------------------------+---------------------------------------------------
Changes (by rransom):

  * priority:  minor => normal


Comment:

 Some possible fixes for this are:

  1. make dirauths keep their old certificates around for a while to be
 served to clients who request them (assuming the directory protocol
 permits this -- it may not);
  2. make clients not complain if they get a sufficiently new certificate,
 even if it's not the one that signed the consensus they have, ''unless''
 they can't get enough of the certificates they need to validate the
 consensus;
  3. make clients not try to download a signing certificate if they (a)
 already have a newer one for that dirauth, and (b) have enough
 certificates to validate the consensus they have.

 This may be related to #5595; if so, option 2 is not actually an option.
 Bumping the priority because of the possible connection to #5595, too.

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