Tor issueshttps://gitlab.torproject.org/tpo/core/tor/-/issues2020-07-23T14:11:07Zhttps://gitlab.torproject.org/tpo/core/tor/-/issues/40061Rebuild fallbackdir list 20202020-07-23T14:11:07ZDavid Gouletdgoulet@torproject.orgRebuild fallbackdir list 2020We ran the call for action: fallback-scripts#30971
This ticket is to merge the new list in `fallback_dirs.inc`
This needs to be backported down to 035.We ran the call for action: fallback-scripts#30971
This ticket is to merge the new list in `fallback_dirs.inc`
This needs to be backported down to 035.Tor: 0.4.5.x-freezeDavid Gouletdgoulet@torproject.orgDavid Gouletdgoulet@torproject.orghttps://gitlab.torproject.org/tpo/core/tor/-/issues/40493fallbackdirs: Update list for October 2021 releases2021-11-14T12:41:19ZDavid Gouletdgoulet@torproject.orgfallbackdirs: Update list for October 2021 releasesWe are about to roll out an 0.3.5.x, 0.4.5.x, 0.4.6.x and 0.4.7.x release. This ticket is to update the lists on all maintained versions.We are about to roll out an 0.3.5.x, 0.4.5.x, 0.4.6.x and 0.4.7.x release. This ticket is to update the lists on all maintained versions.Tor: 0.3.5.x-finalDavid Gouletdgoulet@torproject.orgDavid Gouletdgoulet@torproject.orghttps://gitlab.torproject.org/tpo/core/tor/-/issues/40651Generate new fallbackdir list for 0.4.7.9 release2022-08-03T11:57:55ZRoger DingledineGenerate new fallbackdir list for 0.4.7.9 releaseWe're at about 1/3 failures on the current fallbackdir list. I see that @dgoulet has just requested the directory authorities to prepare for the 0.4.7.9 release. And I think there is a new Tor Browser coming out in August sometime.
All ...We're at about 1/3 failures on the current fallbackdir list. I see that @dgoulet has just requested the directory authorities to prepare for the 0.4.7.9 release. And I think there is a new Tor Browser coming out in August sometime.
All of these are great reasons to do a refresh of the fallbackdir list for these upcoming releases. (Releases plural, since it seems smart to put the refreshed list into 0.4.5 and 0.4.6 too, so LTS Tor users can have their Tor work too.)
Thanks!https://gitlab.torproject.org/tpo/core/tor/-/issues/40447Regenerate fallbackdir list for August 2021 releases2021-08-11T14:05:28ZDavid Gouletdgoulet@torproject.orgRegenerate fallbackdir list for August 2021 releasesThis is simply to track the new fallbackdir list's MR.This is simply to track the new fallbackdir list's MR.David Gouletdgoulet@torproject.orgDavid Gouletdgoulet@torproject.orghttps://gitlab.torproject.org/tpo/core/tor/-/issues/40069Remove Digitalcourage3 relays from fallbackdir list2020-10-22T15:12:33ZDavid Gouletdgoulet@torproject.orgRemove Digitalcourage3 relays from fallbackdir listSomehow they ended up in the list and they were not suppose to. The operator just emailed me about it.
Removal is:
```
9EAD5B2D3DBD96DBC80DCE423B0C345E920A758D
ADB2C26629643DBB9F8FE0096E7D16F9414B4F8D
C2AAB088555850FC434E68943F55107204...Somehow they ended up in the list and they were not suppose to. The operator just emailed me about it.
Removal is:
```
9EAD5B2D3DBD96DBC80DCE423B0C345E920A758D
ADB2C26629643DBB9F8FE0096E7D16F9414B4F8D
C2AAB088555850FC434E68943F551072042B85F1
```David Gouletdgoulet@torproject.orgDavid Gouletdgoulet@torproject.orghttps://gitlab.torproject.org/tpo/core/tor/-/issues/30955Update the fallback entry in the man page2021-07-22T16:19:44ZteorUpdate the fallback entry in the man page"FallbackDir ipv4address:port"
"FallbackDir ipv4address:dirport"
"DirAuthority [nickname] [flags] ipv4address:port"
"DirAuthority [nickname] [flags] ipv4address:dirport"
And similarly for orport.
"The provided port value is a dirport;..."FallbackDir ipv4address:port"
"FallbackDir ipv4address:dirport"
"DirAuthority [nickname] [flags] ipv4address:port"
"DirAuthority [nickname] [flags] ipv4address:dirport"
And similarly for orport.
"The provided port value is a dirport; clients ignore this in favor of the specified "orport=" value."
"Clients always use the orport. Relays prefer the dirport, but will use the orport in some circumstances."
Add something to the FallbackDir entry talking about how the DirPort is used by the checking script?Tor: 0.4.2.x-finalteorteorhttps://gitlab.torproject.org/tpo/core/tor/-/issues/30949Add the source= line to the dir list spec2020-06-27T13:49:57ZteorAdd the source= line to the dir list specIn legacy/trac#30947, we added a source line to the fallback file header.
Now we need to update the spec.In legacy/trac#30947, we added a source line to the fallback file header.
Now we need to update the spec.Tor: 0.4.2.x-finalteorteorhttps://gitlab.torproject.org/tpo/core/tor/-/issues/28795Generate a new fallback list in 2019 and backport it to all supported Tor ver...2020-06-27T13:51: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/tpo/core/tor/-/issues/26688Parse ed25519 IDs in the authority and fallback lists2021-09-16T14:29:03ZteorParse ed25519 IDs in the authority and fallback listshttps://gitlab.torproject.org/tpo/core/tor/-/issues/26685Add ed25519 id support for the hard-coded fallback and authority lists2022-06-16T16:11:23ZteorAdd 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.https://gitlab.torproject.org/tpo/core/tor/-/issues/24839Add a torrc option and descriptor line to opt-in as a FallbackDir2022-03-22T13:28:46ZteorAdd 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 listhttps://gitlab.torproject.org/tpo/core/tor/-/issues/24838Fuzzy match the fallback whitelist2020-06-27T13:54:29ZteorFuzzy 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 legacy/trac#26502.Tor: 0.4.0.x-finalteorteorhttps://gitlab.torproject.org/tpo/core/tor/-/issues/24805Update fallback whitelist in late 20182020-06-27T13:54:31ZteorUpdate fallback whitelist in late 2018We need to update the list using:
* operator emails from 2018
* the opt-in process in legacy/trac#24804
* ~~running the script, finding change warnings, contacting operators, and updating their details~~ we'll do legacy/trac#24838 insteadWe need to update the list using:
* operator emails from 2018
* the opt-in process in legacy/trac#24804
* ~~running the script, finding change warnings, contacting operators, and updating their details~~ we'll do legacy/trac#24838 insteadTor: 0.4.0.x-finalColin ChildsColin Childshttps://gitlab.torproject.org/tpo/core/tor/-/issues/24803Generate a new fallback list in 2018 and backport it to all supported versions2020-06-27T13:54:32ZteorGenerate a new fallback list in 2018 and backport it to all supported versionsThis is the actual list generation ticket.This is the actual list generation ticket.Tor: 0.2.9.x-finalColin ChildsColin Childshttps://gitlab.torproject.org/tpo/core/tor/-/issues/24681Make the default fallback weight in Tor 10.02020-06-27T13:54:38ZteorMake the default fallback weight in Tor 10.0This is a follow-up to legacy/trac#24679.
* update the default weight in parse_dir_fallback_line() to 10.0
* update the man page to reflect the new default
10.0 gives us:
* 0.5% clients bootstrapping off an authority when all fallbacks...This is a follow-up to legacy/trac#24679.
* update the default weight in parse_dir_fallback_line() to 10.0
* update the man page to reflect the new default
10.0 gives us:
* 0.5% clients bootstrapping off an authority when all fallbacks are up, * 2% when 25% are down (our replacement threshold)
* 7% when 40% are down (our worst case scenario)Tor: 0.3.3.x-finalteorteorhttps://gitlab.torproject.org/tpo/core/tor/-/issues/23471Add ed25519 ids to torrc relay configs2020-06-27T13:55:41ZteorAdd ed25519 ids to torrc relay configsTor relays have ed25519 keys, but there is no way to add them to the torrc (or the hard-coded configs compiled into tor).
Tor accepts at least 3 types of hard-coded relay lists in its configs:
* Directory Authorities
* Fallback Director...Tor relays have ed25519 keys, but there is no way to add them to the torrc (or the hard-coded configs compiled into tor).
Tor accepts at least 3 types of hard-coded relay lists in its configs:
* Directory Authorities
* Fallback Directory Mirrors
* BridgesTor: 0.3.3.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/22760Fix extra-info flags on fallbacks2021-09-16T14:31:59ZteorFix extra-info flags on fallbacksSee the first comment for details.See the first comment for details.https://gitlab.torproject.org/tpo/core/tor/-/issues/22421Update fallback config comment for exponential backoff2020-06-27T13:56:32ZteorUpdate fallback config comment for exponential backoffWe modified the fallback behaviour when we merged the exponential backoff code in 0.2.9.1-alpha, and again in legacy/trac#17750:
```
/* With the ClientBootstrapConsensus*Download* below:
* Clients with only authorities will try:
* ...We modified the fallback behaviour when we merged the exponential backoff code in 0.2.9.1-alpha, and again in legacy/trac#17750:
```
/* With the ClientBootstrapConsensus*Download* below:
* Clients with only authorities will try:
* - 3 authorities over 10 seconds, then wait 60 minutes.
* Clients with authorities and fallbacks will try:
* - 2 authorities and 4 fallbacks over 21 seconds, then wait 60 minutes.
* Clients will also retry when an application request arrives.
* After a number of failed reqests, clients retry every 3 days + 1 hour.
*
* Clients used to try 2 authorities over 10 seconds, then wait for
* 60 minutes or an application request.
*
* When clients have authorities and fallbacks available, they use these
* schedules: (we stagger the times to avoid thundering herds) */
V(ClientBootstrapConsensusAuthorityDownloadSchedule, CSV_INTERVAL,
"6, 11, 3600, 10800, 25200, 54000, 111600, 262800" /* 3 days + 1 hour */),
V(ClientBootstrapConsensusFallbackDownloadSchedule, CSV_INTERVAL,
"0, 1, 4, 11, 3600, 10800, 25200, 54000, 111600, 262800"),
/* When clients only have authorities available, they use this schedule: */
V(ClientBootstrapConsensusAuthorityOnlyDownloadSchedule, CSV_INTERVAL,
"0, 3, 7, 3600, 10800, 25200, 54000, 111600, 262800"),
```
The behaviour is now:
```
/* With the ClientBootstrapConsensus*Download* below:
* Clients with only authorities will try:
* - at least 3 authorities over 10 seconds, then exponentially backoff,
* with the next attempt 3-21 seconds later,
* Clients with authorities and fallbacks will try:
* - at least 2 authorities and 4 fallbacks over 21 seconds, then
* exponentially backoff, with the next attempts 4-33 seconds later,
* Clients will also retry when an application request arrives.
* After a number of failed requests, clients retry every 3 days + 1 hour.
*
* Clients used to try 2 authorities over 10 seconds, then wait for
* 60 minutes or an application request.
```Tor: 0.3.1.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/22270Fix the usage message in the fallback directory script2020-06-27T13:56:38ZteorFix the usage message in the fallback directory scriptTor: 0.3.1.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/22268TROVE-2017-003: Impersonation of a single fallback directory mirror2020-06-27T13:56:38ZteorTROVE-2017-003: Impersonation of a single fallback directory mirrorSee:
https://lists.torproject.org/pipermail/tor-relays/2017-May/012281.htmlSee:
https://lists.torproject.org/pipermail/tor-relays/2017-May/012281.htmlTor: 0.3.1.x-final