[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #3327 [Tor Relay]: Overzealous descriptor regeneration bug remains
#3327: Overzealous descriptor regeneration bug remains
-----------------------+----------------------------------------------------
Reporter: arma | Owner:
Type: defect | Status: needs_review
Priority: major | Milestone: Tor: 0.2.2.x-final
Component: Tor Relay | Version:
Keywords: | Parent:
Points: | Actualpoints:
-----------------------+----------------------------------------------------
Comment(by arma):
bug3327 looks reasonable. I'd suggest making it a 'major' feature, and
changing 'our' to 'their' in the changes file. And maybe s/Routers/Relays/
while we're at it.
Note that we're going to see more publication attempts, and thus more
descriptors in the wild, in some cases. The first case that comes to mind
is a relay that thinks it's reachable but a quorum of directory
authorities can't reach it. I expect we'll see 12 times as many
descriptors for those relays. Clients won't see them, so it's not so bad,
but karsten's metrics datasets will bloat. I wonder if relays that cache
v2 data will fetch them too, if tor26 thinks they're reachable.
It sure will be tricky to figure out if this patch is working right, since
it only kicks in for the case that we don't think exists much right now. I
wonder if we might tell the directory authority our reason for generating
the new descriptor, e.g. as an http header when we post? That would let us
keep a better eye on whether (and for whom) this patch is seeing action.
I agree that we'll be happier putting this feature into 0.2.3.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/3327#comment:15>
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