#535: servers should support hearing "not new descriptor" --------------------------------+------------------------------------------- Reporter: arma | Type: defect Status: new | Priority: major Milestone: Tor: 0.2.2.x-final | Component: Tor Relay Version: 0.2.0.8-alpha | Resolution: None Keywords: | Parent: #3327 Points: | Actualpoints: --------------------------------+------------------------------------------- Changes (by nickm):
* priority: critical => major Comment: If we want this in 0.2.2.x, the changes need to be MUCH MUCH smaller than adding new callbacks, changing interfaces, etc. We already have the code in connection_dir_reached_eof that gets called on every response from the dirserver. I'd like to change the architecture, but not for 0.2.2. So, what's the correct actual behavior here? We want to remember, for each authority, the 'published' time of the last descriptor that it accepted from us. We want to have another global in router.c, something like "desc_clean_since", that remembers the last time that we had our descriptor accepted by sufficient authorities. We can then replace "mark_my_descriptor_dirty_of_older_than" with a new function that declares the descriptor to be dirty if it is too old, OR if too much time has passed since sufficient authorities accepted one of our descriptors. Or another option is to look at the publication time for the version of our descriptor that's listed in the directory consensus. This could probably use some pseudocode. Also, it feels like something to do as a branch that gets merged first to 0.2.3.x for testing, then back to 0.2.2.x: none of the solutions here feel as obvious and straightforwardly harmless as I'd want. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/535#comment:7> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online _______________________________________________ tor-bugs mailing list [email protected] https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
