[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #8240 [Tor]: Raise our guard rotation period
#8240: Raise our guard rotation period
----------------------------------------------------+-----------------------
Reporter: arma | Owner:
Type: defect | Status: needs_revision
Priority: major | Milestone: Tor: 0.2.4.x-final
Component: Tor | Version:
Keywords: tor-client needs-proposal 023-backport | Parent:
Points: | Actualpoints:
----------------------------------------------------+-----------------------
Comment(by mikeperry):
Replying to [comment:13 arma]:
> Replying to [comment:11 mikeperry]:
> > I'm not talking about the "Bandwidth=" weights. I'm talking about the
flag weights. In fact, it appears to me that I am suggesting exactly the
same thing you are, just using a different mechanism (one that existing
clients already obey today).
>
> Great. What do we change in these weights then? I still don't see with
these system-wide weights how we can tell clients to still back off from
using a Guard-for-a-long-time relay for other path positions, but not back
off so much from using a Guard-for-just-a-short-time relay for other path
positions.
Ugh, I think I have braindamage from juggling too many things. You're
right, individual relays can't be re-weighted in this way currently. We
would need client side changes for what I described: we'd need to get the
duration that each node has had the Guard flag to the client somehow, and
then the client would have to adjust that node's W*g* weights themselves..
Either way, it's not something we'd do on the 0.2.4.x timescale. For now,
we should avoid raising the new limit too far beyond its current value..
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/8240#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