Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T16:05:53Zhttps://gitlab.torproject.org/legacy/trac/-/issues/20910Make the fallback list automatically adapt to minor changes2020-06-13T16:05:53ZteorMake the fallback list automatically adapt to minor changesI spend a lot of time contacting relay operators about new and changed IP addresses, fingerprints, etc.
It would be great to identify minor changes (such as adding an IPv6 address) and automatically adapt to them, rather than eliminatin...I spend a lot of time contacting relay operators about new and changed IP addresses, fingerprints, etc.
It would be great to identify minor changes (such as adding an IPv6 address) and automatically adapt to them, rather than eliminating the relay from the list. In the case of an IPv6 address, automatically adding it should be OK.Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/20908Display the fingerprint when downloading consensuses from fallbacks2020-06-13T15:04:06ZteorDisplay the fingerprint when downloading consensuses from fallbacksJust using this for the bug number, will be fixed in #18828.Just using this for the bug number, will be fixed in #18828.Tor: 0.3.1.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/20897Make it easier to check the entire fallback whitelist for errors2020-06-13T16:05:52ZteorMake it easier to check the entire fallback whitelist for errorsThere are instructions for modifying the fallback script to scan the entire whitelist in:
https://trac.torproject.org/projects/tor/wiki/doc/UpdatingFallbackDirectoryMirrors
It would be great if we automated these.There are instructions for modifying the fallback script to scan the entire whitelist in:
https://trac.torproject.org/projects/tor/wiki/doc/UpdatingFallbackDirectoryMirrors
It would be great if we automated these.Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/20883Ignore relays without contact info when emailing potential fallback operators2020-06-13T16:05:52ZteorIgnore relays without contact info when emailing potential fallback operatorsSometimes, we want to do a mail-out to (potential) fallback operators.
We might want to skip operators without contact details.
Or we might want to leave them in there, so we know the how many operators we can't contact.Sometimes, we want to do a mail-out to (potential) fallback operators.
We might want to skip operators without contact details.
Or we might want to leave them in there, so we know the how many operators we can't contact.https://gitlab.torproject.org/legacy/trac/-/issues/20882Make output sort order of fallbacks configurable2020-06-13T16:05:51ZteorMake output sort order of fallbacks configurableImplemented in #18828.Implemented in #18828.teorteorhttps://gitlab.torproject.org/legacy/trac/-/issues/20881Select 200 fallbacks for each release2020-06-13T16:05:51ZteorSelect 200 fallbacks for each releaseThis allows us to remove fallbacks as needed for 6-12 months, without the list getting too small.
Implemented in #18828.This allows us to remove fallbacks as needed for 6-12 months, without the list getting too small.
Implemented in #18828.teorteorhttps://gitlab.torproject.org/legacy/trac/-/issues/20880Make minimum fallback stability 6 months2020-06-13T16:05:51ZteorMake minimum fallback stability 6 monthsNow that we've fixed #18050, we can revert the fallback minimum address stability to a longer period. I suggest 6 months - the period between releases.
This will be implemented as part of #18828.Now that we've fixed #18050, we can revert the fallback minimum address stability to a longer period. I suggest 6 months - the period between releases.
This will be implemented as part of #18828.teorteorhttps://gitlab.torproject.org/legacy/trac/-/issues/20878Add bandwidth to fallback comments2020-06-13T16:05:50ZteorAdd bandwidth to fallback commentsImplemented as part of #18828Implemented as part of #18828teorteorhttps://gitlab.torproject.org/legacy/trac/-/issues/20877Fix a bug in updateFallbackDirs.py's comment handling2020-06-13T16:05:50ZteorFix a bug in updateFallbackDirs.py's comment handlingTurns out we weren't returning the comment string. Oops!
Bugfix on 99983432 in tor-0.2.8.3-alpha.Turns out we weren't returning the comment string. Oops!
Bugfix on 99983432 in tor-0.2.8.3-alpha.teorteorhttps://gitlab.torproject.org/legacy/trac/-/issues/20876Avoid contacting fallback operators who are unlikely to be accepted2020-06-13T16:05:49ZteorAvoid contacting fallback operators who are unlikely to be acceptedAfter we automatically calculate the fallback threshold in #20192, it would be great to update that threshold based on whether the operator would be selected if they opted-in.After we automatically calculate the fallback threshold in #20192, it would be great to update that threshold based on whether the operator would be selected if they opted-in.Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/20539Make sure fallback directories aren't running buggy versions / can deliver a ...2020-06-13T16:05:49ZteorMake sure fallback directories aren't running buggy versions / can deliver a recent consensusAfter #20499, we should reject fallback directories that deliver a consensus outdated by more than N hours, where N is one of [1, 2, 3].After #20499, we should reject fallback directories that deliver a consensus outdated by more than N hours, where N is one of [1, 2, 3].https://gitlab.torproject.org/legacy/trac/-/issues/20194Add "update fallbacks" to "Preliminaries" in Tor's doc/HACKING/ReleasingTor.md2020-06-13T15:01:37ZteorAdd "update fallbacks" to "Preliminaries" in Tor's doc/HACKING/ReleasingTor.mdWhen we added fallback directory mirrors, we should have also listed them as something we need to update every major release:
2. Early in the alpha series for each new major release, at least a month before the code freeze, update th...When we added fallback directory mirrors, we should have also listed them as something we need to update every major release:
2. Early in the alpha series for each new major release, at least a month before the code freeze, update the list of fallback directory mirrors using the instructions in: https://trac.torproject.org/projects/tor/wiki/doc/UpdatingFallbackDirectoryMirrorsTor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/20192When outputting potential new fallbacks, blacklist the whitelist2020-06-13T16:05:48ZteorWhen outputting potential new fallbacks, blacklist the whitelistWhen we look for potential new fallback directory mirrors, we want to ignore existing whitelisted fallbacks, as well as the blacklist.When we look for potential new fallback directory mirrors, we want to ignore existing whitelisted fallbacks, as well as the blacklist.Tor: unspecifiedhaxxpophaxxpophttps://gitlab.torproject.org/legacy/trac/-/issues/20190Remove broken fallbacks from the 0.2.8 list2020-06-13T16:05:47ZteorRemove broken fallbacks from the 0.2.8 listPlease merge my branch broken-028-fallbacks to both 0.2.8 and master.
It comments-out fallbacks that have broken since I last checked in just before 0.2.8.6.Please merge my branch broken-028-fallbacks to both 0.2.8 and master.
It comments-out fallbacks that have broken since I last checked in just before 0.2.8.6.Tor: 0.2.8.x-finalteorteorhttps://gitlab.torproject.org/legacy/trac/-/issues/20178The fallback update script should log stem connection errors at warning level2020-06-13T16:05:47ZteorThe fallback update script should log stem connection errors at warning levelCurrently, they're logged at info-level, in order to filter out the "connecting to" messages. It would be great to keep those at info level, and log the "error connecting" messages at WARNING level.Currently, they're logged at info-level, in order to filter out the "connecting to" messages. It would be great to keep those at info level, and log the "error connecting" messages at WARNING level.Tor: unspecifiedhaxxpophaxxpophttps://gitlab.torproject.org/legacy/trac/-/issues/20177When checking existing fallbacks, report those fallbacks at warning log level2020-06-13T16:05:46ZteorWhen checking existing fallbacks, report those fallbacks at warning log levelWhen the fallback script excludes some relays, it only logs at info level. This is usually what we want, but when checking existing fallbacks, it would be great to see any message about those fallbacks at WARNING log level.
This would m...When the fallback script excludes some relays, it only logs at info level. This is usually what we want, but when checking existing fallbacks, it would be great to see any message about those fallbacks at WARNING log level.
This would make it easier to work out why fallbacks are broken.Tor: unspecifiedhaxxpophaxxpophttps://gitlab.torproject.org/legacy/trac/-/issues/20175Allow the fallback script to ignore temporary IPv6 addresses2020-06-13T16:05:45ZteorAllow the fallback script to ignore temporary IPv6 addressesWhen updateFallbackDirs.py checks relay addresses, it makes sure that the IPv4 and IPv6 addresses and ports match the relay's whitelist entry.
If a relay's IPv6 address is temporary, it should not be included in the whitelist.
But this...When updateFallbackDirs.py checks relay addresses, it makes sure that the IPv4 and IPv6 addresses and ports match the relay's whitelist entry.
If a relay's IPv6 address is temporary, it should not be included in the whitelist.
But this means the relay will never be selected, because its descriptor has an IPv6 address, and that address doesn't match the (missing) address in the whitelist.
We should add a way to say ipv6=ignored or something.Tor: unspecifiedhaxxpophaxxpophttps://gitlab.torproject.org/legacy/trac/-/issues/20174Automate checking existing fallbacks2020-06-13T16:05:45ZteorAutomate checking existing fallbacksI use a manual process to check existing fallbacks. It would be great if the updateFallbackDirs.py script would automatically read src/or/fallback_dirs.inc, and check each fallback for errors.
For details, see:
https://trac.torproject.o...I use a manual process to check existing fallbacks. It would be great if the updateFallbackDirs.py script would automatically read src/or/fallback_dirs.inc, and check each fallback for errors.
For details, see:
https://trac.torproject.org/projects/tor/wiki/doc/UpdatingFallbackDirectoryMirrors
I think it can go in 0.3.0Tor: 0.3.0.x-finalhaxxpophaxxpophttps://gitlab.torproject.org/legacy/trac/-/issues/20173Tell 0.2.9 fallback directory operators that their relays are on the list2020-06-13T16:05:44ZteorTell 0.2.9 fallback directory operators that their relays are on the listThank them, and remind them to keep their relay details the same.
I am hoping the community team can help me out with this, if I provide a list.Thank them, and remind them to keep their relay details the same.
I am hoping the community team can help me out with this, if I provide a list.teorteorhttps://gitlab.torproject.org/legacy/trac/-/issues/20172Fallback Tasks for 20162020-06-13T15:01:34ZteorFallback Tasks for 2016This is the top-level task for fallback directory mirror tickets in 2016, typically in 0.2.8 or 0.2.9.This is the top-level task for fallback directory mirror tickets in 2016, typically in 0.2.8 or 0.2.9.Tor: unspecified