[tor-relays] Fallback directory mirror DFRI7 is dead

[teor]

> On 25 Aug 2017, at 15:29, Roger Dingledine <arma at mit.edu> wrote:
> 
> On Fri, Aug 25, 2017 at 11:43:10AM +1000, teor wrote:
>>> A new DFRI7 will appear on the same address and port within a couple of
>>> days. Should I simply update fallback_dirs.inc?
>> 
>> No need to do anything right away!
> 
> Will it be bad to have a new relay (with a new key), on the same IP:port
> as what many clients think is an existing fallback relay?

The new relay won't be eligible for the list until it's been up for
at least a month. And it will take time to build up bandwidth weight.

Since DFRI has a few eligible relays, we will probably choose different
ones in the next list.

> I can imagine clients getting warnings in their logs, about how they're
> getting an unexpected fingerprint while attempting to connect.

Since 0.2.8.5-rc, Tor logs an info-level message saying that we'll try
another fallback:
https://trac.torproject.org/projects/tor/ticket/18812#comment:8

T

--
Tim Wilson-Brown (teor)

teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
xmpp: teor at torproject dot org
------------------------------------------------------------------------



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20170826/e0b1f8c5/attachment.sig>