On 25 Aug 2017, at 09:23, Linus Nordberg linus@nordberg.se wrote:
Hi teor,
Fallback directory mirror DFRI7 [0] is down, due to multiple disk krashes, since about 30h and will not come alive with the same key.
[0] 171.25.193.131:80 orport=443 id=79861CF8522FC637EF046F7688F5289E49D94576
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!
We do a fallback refresh every 6-12 months. The list is backported to 0.2.8 and later, and goes out in the next patch release.
I've updated the ticket [1] we're using to track whitelist changes. There is also a master ticket [2] for the 0.3.2 or 0.3.3 fallback refresh.
We try to keep 90% of fallbacks available, and we're currently at about 88% [3]. (The network can cope with 50% of the fallbacks being down, but it puts load on the authorities.)
So we'll do a refresh [4] some time in the next few months. It would be great to get it done in September for the 0.3.2 alpha series [5].
If anyone wants to help generate the list, the instructions are at [4] in section 3b. (We wrote longer instructions, but they took a lot of time, without adding much value.)
Tim
[1]: https://trac.torproject.org/projects/tor/ticket/22321#comment:4 [2]: https://trac.torproject.org/projects/tor/ticket/22271 [3]: https://consensus-health.torproject.org/graphs.html (Needs JS, SVG) [4]: https://trac.torproject.org/projects/tor/wiki/doc/UpdatingFallbackDirectoryM... [5]: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTorR...
Tim
T -- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n ------------------------------------------------------------------------