<div dir="ltr">Sorry - that was crass. Thanks for the attempt, but I've read those documents. Specifically, I'm looking into what has changed, if anything. Is it just below the threshold of the Weighted Uptime? (e.g. we have enough Guards?) I asked because I was told that the bwauth issues were holding people back before (because everyone was unmeasured). Since that was resolved but still no guard flag, I was becoming curious.<div><br></div><div>I'll just sit back and wait some more.</div><div>Matt</div></div><br><div class="gmail_quote"><div dir="ltr">On Wed, Mar 21, 2018 at 1:23 PM Vasilis <<a href="mailto:andz@torproject.org">andz@torproject.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Matthew,<br>
<br>
Matthew Glennon:<br>
> While I understand that my relay lost the guard flag because of a weekend<br>
> of downtime, I would expect that it would get it back after a while of<br>
> stable again? Anyone able to shed some light on when it will get the flag<br>
> back?<br>
> <a href="https://metrics.torproject.org/rs.html#details/924B24AFA7F075D059E8EEB284CC400B33D3D036" rel="noreferrer" target="_blank">https://metrics.torproject.org/rs.html#details/924B24AFA7F075D059E8EEB284CC400B33D3D036</a><br>
<br>
"Directory authorities assign the Guard flag to relays based on three<br>
characteristics: "bandwidth" (they need to have a large enough consensus<br>
weight), "weighted fractional uptime" (they need to be working most of the<br>
time), and "time known" (to make attacks more expensive, we don't want to give<br>
the Guard flag to relays that haven't been around a while first). This last<br>
characteristic is most relevant here: on today's Tor network, you're first<br>
eligible for the Guard flag on day eight."<br>
<br>
I will suggest you to read the lifecycle of the new relay post [1], the Guard<br>
FAQ [2] and the guard flag section of the directory protocol [3].<br>
<br>
[1] <a href="https://blog.torproject.org/lifecycle-new-relay" rel="noreferrer" target="_blank">https://blog.torproject.org/lifecycle-new-relay</a><br>
[2] <a href="https://www.torproject.org/docs/faq#EntryGuards" rel="noreferrer" target="_blank">https://www.torproject.org/docs/faq#EntryGuards</a><br>
[3] <a href="https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n2490" rel="noreferrer" target="_blank">https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n2490</a><br>
<br>
Hope this helps.<br>
<br>
<br>
Cheers,<br>
~Vasilis<br>
--<br>
Fingerprint: 8FD5 CF5F 39FC 03EB B382 7470 5FBF 70B1 D126 0162<br>
Pubkey: <a href="https://pgp.mit.edu/pks/lookup?op=get&search=0x5FBF70B1D1260162" rel="noreferrer" target="_blank">https://pgp.mit.edu/pks/lookup?op=get&search=0x5FBF70B1D1260162</a><br>
<br>
<br>
<br>
_______________________________________________<br>
tor-relays mailing list<br>
<a href="mailto:tor-relays@lists.torproject.org" target="_blank">tor-relays@lists.torproject.org</a><br>
<a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays" rel="noreferrer" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a><br>
</blockquote></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Matthew Glennon<div>matthew@glennon.online</div><div>PGP Signing Available Upon Request<br><a href="https://keybase.io/crazysane">https://keybase.io/crazysane</a><br></div></div></div>