Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T16:06:39Zhttps://gitlab.torproject.org/legacy/trac/-/issues/28986Log at info level in list generation mode2020-06-13T16:06:39ZteorLog at info level in list generation modestarlight suggests that we log at info level by default:
https://trac.torproject.org/projects/tor/ticket/28795#comment:4
We can make the same change in check_existing mode if we like.starlight suggests that we log at info level by default:
https://trac.torproject.org/projects/tor/ticket/28795#comment:4
We can make the same change in check_existing mode if we like.https://gitlab.torproject.org/legacy/trac/-/issues/28797Set up CI on the fallback script with a small number of relays2020-06-13T16:06:37ZteorSet up CI on the fallback script with a small number of relaysWe should test the list generation and check_existing modes, with a few relays (10?).We should test the list generation and check_existing modes, with a few relays (10?).https://gitlab.torproject.org/legacy/trac/-/issues/28796Move the fallback script and whitelist into its own repository2020-06-13T16:06:36ZteorMove the fallback script and whitelist into its own repositoryWe'd like to move the fallback script and whitelist into its own repository. Then we can make changes as needed, rather than queueing changes on large branches.
We can also set up CI to test the script with a small number of relays.We'd like to move the fallback script and whitelist into its own repository. Then we can make changes as needed, rather than queueing changes on large branches.
We can also set up CI to test the script with a small number of relays.Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/28795Generate a new fallback list in 2019 and backport it to all supported Tor ver...2020-06-13T15:35:26ZteorGenerate a new fallback list in 2019 and backport it to all supported Tor versionsWe usually get two people to run:
```
scripts/maint/updateFallbackDirs.py > src/or/fallback_dirs.inc 2> fallback_dirs.log
```
from two different locations, then merge the lists.
Please attach the logs to this ticket.We usually get two people to run:
```
scripts/maint/updateFallbackDirs.py > src/or/fallback_dirs.inc 2> fallback_dirs.log
```
from two different locations, then merge the lists.
Please attach the logs to this ticket.Tor: 0.2.9.x-finalteorteorhttps://gitlab.torproject.org/legacy/trac/-/issues/28794Run an opt-in process for relay operators to become fallbacks in 20192020-06-13T16:06:36ZteorRun an opt-in process for relay operators to become fallbacks in 2019Mail tor-relays and asking if stable relay operators want to become fallbacks. Then update fallback whitelist based on the opt-ins.Mail tor-relays and asking if stable relay operators want to become fallbacks. Then update fallback whitelist based on the opt-ins.teorteorhttps://gitlab.torproject.org/legacy/trac/-/issues/28793Rebuild the fallback list in 20192020-06-13T16:06:34ZteorRebuild the fallback list in 2019We need to rebuild the list of fallbacks in mid or late 2019.
We usually do this when 25% or more go down.
(When 25% of fallbacks are down, a warning is logged daily in #tor-bots on IRC.)
Here are the instructions for running a rebuild:...We need to rebuild the list of fallbacks in mid or late 2019.
We usually do this when 25% or more go down.
(When 25% of fallbacks are down, a warning is logged daily in #tor-bots on IRC.)
Here are the instructions for running a rebuild:
https://trac.torproject.org/projects/tor/wiki/doc/UpdatingFallbackDirectoryMirrorsTor: unspecifiedteorteorhttps://gitlab.torproject.org/legacy/trac/-/issues/28768Update fallback script to match Tor bootstrap changes2020-06-13T16:06:33ZteorUpdate fallback script to match Tor bootstrap changesIn #24661, we make clients bootstrap from reasonably old consensuses (expired in the last 24 hours).
In #28591, we make clients accept future consensuses as long as they're reasonably future consensuses (valid up to 24 hours in the futu...In #24661, we make clients bootstrap from reasonably old consensuses (expired in the last 24 hours).
In #28591, we make clients accept future consensuses as long as they're reasonably future consensuses (valid up to 24 hours in the future), and relays serve those consensuses.
We need to change the fallback checks to match these changes in Tor.Tor: 0.4.0.x-finalteorteorhttps://gitlab.torproject.org/legacy/trac/-/issues/27914Extract fallback-scripts to its own git repository2020-06-13T16:06:32ZNick MathewsonExtract fallback-scripts to its own git repositoryThis would let us give teor and phoul direct commit permissions here.This would let us give teor and phoul direct commit permissions here.Tor: 0.4.0.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/27737Manually remove 64.113.32.29 from the generated fallback list2020-06-13T16:06:31ZteorManually remove 64.113.32.29 from the generated fallback listIf 64.113.32.29 hasn't changed to 198.232.165.2 yet, we should manually remove it from the generated fallback list.If 64.113.32.29 hasn't changed to 198.232.165.2 yet, we should manually remove it from the generated fallback list.Tor: 0.3.5.x-finalteorteorhttps://gitlab.torproject.org/legacy/trac/-/issues/26688Parse ed25519 IDs in the authority and fallback lists2020-06-13T15:27:41ZteorParse ed25519 IDs in the authority and fallback listsTor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/26687Output ed25519 IDs in the authority and fallback lists2020-06-13T16:06:30ZteorOutput ed25519 IDs in the authority and fallback listshttps://gitlab.torproject.org/legacy/trac/-/issues/26686Add ed25519 ids to the fallback whitelist2020-06-13T16:06:30ZteorAdd ed25519 ids to the fallback whitelistThe fallback scripts should parse ed25519 ids from the fallback whitelist, and check both the RSA id and ed25519 id.The fallback scripts should parse ed25519 ids from the fallback whitelist, and check both the RSA id and ed25519 id.https://gitlab.torproject.org/legacy/trac/-/issues/26685Add ed25519 id support for the hard-coded fallback and authority lists2020-06-13T15:27:41ZteorAdd ed25519 id support for the hard-coded fallback and authority listsThis is the parent ticket for getting ed25519 id support in Tor's hard-coded directory lists.This is the parent ticket for getting ed25519 id support in Tor's hard-coded directory lists.Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/26502Stop using the fallback blacklist, and delete it2020-06-13T16:06:29ZteorStop using the fallback blacklist, and delete itWe require relay operators to opt-in to being fallbacks, and we won't ever switch to opt-out. (See #24789.)
So we don't need the fallback blacklist any more.
We should stop loading the blacklist in the script, then delete it.We require relay operators to opt-in to being fallbacks, and we won't ever switch to opt-out. (See #24789.)
So we don't need the fallback blacklist any more.
We should stop loading the blacklist in the script, then delete it.Tor: 0.3.5.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/25798Remove from fallback list:2020-06-13T16:06:29ZTracRemove from fallback list:Relay treadstone (185.129.249.124) has been shut down by my provider and unlikely to be back (the website of the provider, including the control panel has been gone for days). Please remove from the fallback list.
**Trac**:
**Username...Relay treadstone (185.129.249.124) has been shut down by my provider and unlikely to be back (the website of the provider, including the control panel has been gone for days). Please remove from the fallback list.
**Trac**:
**Username**: iomegaTor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/24953In check_existing mode, log "fallback list", not "whitelist"2020-06-13T16:06:26ZteorIn check_existing mode, log "fallback list", not "whitelist"This confused at least one relay operator.This confused at least one relay operator.Tor: 0.4.0.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/24839Add a torrc option and descriptor line to opt-in as a FallbackDir2020-06-13T16:06:51ZteorAdd a torrc option and descriptor line to opt-in as a FallbackDirThis needs:
* a proposal and a design
* a patch to dir-spec.txt
* a patch to the tor man page
* a tor code patch
* an updateFallbackDirs.py code patch
* a wiki update to [[doc/UpdatingFallbackDirectoryMirrors]]
Here's a quick sketch of ...This needs:
* a proposal and a design
* a patch to dir-spec.txt
* a patch to the tor man page
* a tor code patch
* an updateFallbackDirs.py code patch
* a wiki update to [[doc/UpdatingFallbackDirectoryMirrors]]
Here's a quick sketch of a design:
1. Relay operators set `OfferFallbackDir 1` to offer their relay as a potential FallbackDir.
2. Relays with this option set put `offer-fallback-dir` in their descriptors
3. updateFallbackDirs.py loads relay fingerprints with `offer-fallback-dir`, and from the legacy offer list
4. updateFallbackDirs.py does stability checks, and generates the fallback listTor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/24838Fuzzy match the fallback whitelist2020-06-13T15:20:06ZteorFuzzy match the fallback whitelistWe can rely on Onionoo to tell us when relay fingerprints or addresses change, so we don't need to do an exact match.
But listing fingerprints, addresses and ports in the whitelist is useful so that we know what a relay operator origina...We can rely on Onionoo to tell us when relay fingerprints or addresses change, so we don't need to do an exact match.
But listing fingerprints, addresses and ports in the whitelist is useful so that we know what a relay operator originally asked for.
Fuzzy matching simplifies maintaining the fallback whitelist, because we don't have to ask operators to update their relay details. (Or ask if those details are permanent.)
We deleted the blacklist in #26502.Tor: 0.4.0.x-finalteorteorhttps://gitlab.torproject.org/legacy/trac/-/issues/24805Update fallback whitelist in late 20182020-06-13T15:19:52ZteorUpdate fallback whitelist in late 2018We need to update the list using:
* operator emails from 2018
* the opt-in process in #24804
* ~~running the script, finding change warnings, contacting operators, and updating their details~~ we'll do #24838 insteadWe need to update the list using:
* operator emails from 2018
* the opt-in process in #24804
* ~~running the script, finding change warnings, contacting operators, and updating their details~~ we'll do #24838 insteadTor: 0.4.0.x-finalColin ChildsColin Childshttps://gitlab.torproject.org/legacy/trac/-/issues/24804Run an opt-in process for relay operators to become fallbacks in 20182020-06-13T16:06:25ZteorRun an opt-in process for relay operators to become fallbacks in 2018This involves mailing tor-relays and asking if stable relay operators want to become fallbacks.This involves mailing tor-relays and asking if stable relay operators want to become fallbacks.Tor: 0.4.0.x-finalColin ChildsColin Childs