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

Re: [tor-bugs] #2467 [Tor Weather]: torweather refuses to accept the fingerprint of my relay.



#2467: torweather refuses to accept the fingerprint of my relay.
-------------------------+--------------------------------------------------
 Reporter:  murble       |       Owner:  kaner   
     Type:  defect       |      Status:  accepted
 Priority:  critical     |   Milestone:          
Component:  Tor Weather  |     Version:          
 Keywords:  fingerprint  |      Points:          
   Parent:               |  
-------------------------+--------------------------------------------------

Comment(by mikeperry):

 It looks like what kaner described is the opposite problem to what arma
 mentioned. Kaner's log has the descriptor but not the consensus entry.
 This could be because the descriptor in question is hibernating (this one
 in particular has an observed bw of 0, which makes me think it is either
 hibernating or just finishing hibernating). To solve this problem, you
 probably need FetchUselessDescriptors to be set, and to work properly.
 arma and sebastian seem to believe there's a chance it may not, if tor26
 goes down (and/or other situations?).

 Wrt the issue of not seeing fingerprints that are in the consensus, you
 probably want to set both FetchDirInfoExtraEarly and FetchDirInfoEarly to
 ensure you get a consensus every hour. For whatever reason, both of these
 config options are actually needed to get hourly consensus data. At least
 that's what it appeared to me while looking at the source.

 Wrt to what TorCtl does for the BW auths, I implemented a
 ConsensusTrackerListener in SQLSupport.py that actually doesn't consider
 the consensus to be ready until the Tor client goes at least 60 seconds
 without telling the control port about new descriptors *and* we have 95%
 of the descriptors from the consensus (this is because there is no actual
 tor control port event to say that Tor has decided it is done downloading
 descriptors). You probably don't want/need that SQLSupport code, but maybe
 a hack like this would help, too?

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