Age | Commit message (Collapse) | Author |
|
(It becomes irrelevant on 15 May 2018 when 0.2.5 is EOL.)
|
|
|
|
Implements ticket 24791
|
|
Avoid selecting fallbacks that change their IP addresses too often.
Select more fallbacks by ignoring the Guard flag, and allowing lower
cutoffs for the Running and V2Dir flags. Also allow a lower bandwidth,
and a higher number of fallbacks per operator (5% of the list).
Implements ticket 24785.
|
|
Comment-only change.
Implements #24711.
|
|
(Some OSs don't put it in /usr/bin.)
Fixes bug 24708; bugfix on 0.2.8.1-alpha.
|
|
This can act as a revision counter, as requested by atagar in 24742.
Part of 24725.
|
|
Part of #24725.
|
|
This helps external parsers.
Also, add comments indicating where to add new fields in the fallback
format.
Part of 24725.
|
|
This makes sure that list parsers only see one comma per fallback entry,
and only see one equals sign per field.
Implements ticket 24726.
|
|
This allows stem to use fallbacks to fetch extra-info documents,
rather than using authorities.
Implements ticket 22759.
|
|
This makes it easier for operators to find their relays, and allows stem to
use nicknames to identify fallbacks.
Implements ticket 24600.
|
|
This removes some redundant repeated lines.
Ticket 24681 will maintain the current fallback weights by changing
Tor's default fallback weight to 10.
Implements ticket 24679.
|
|
This helps external parsers like stem and Relay Search.
Implements ticket 24725.
|
|
|
|
|
|
|
|
Comment-only change.
Closes 24682.
|
|
Decrease the minimum number of fallbacks to 100.
Final fix to 20913.
|
|
|
|
And explain what it does.
Fixes bug 22270 in 0.3.0.3-alpha.
|
|
Increase the fallback stability requirement to 30 days.
When this was at 7 days, we chose far too many unstable fallbacks.
Decrease the guard flag requirement to 0.8.
When this was at 0.9, we lost too many fallbacks due to version upgrades.
(The running and v2dir flags ensure DirPorts are available to clients.)
Partial fixes to #20913.
|
|
|
|
|
|
|
|
|
|
Sometimes, the fallback generation script doesn't add attributes to the
fallbacks in the list. If this happens, log an error, and avoid selecting
that fallback.
This is a rare issue: it should not change selection behaviour.
Fixes issue #20945.
|
|
This works around #20909, where relays serve stale consensuses for a short
time, and then recover.
Update to the fix for #20539.
|
|
Exclude relays that have been down for 1 or more days from the fallback
candidate list.
When a relay operator has multiple relays, this prioritises relays that are
up over relays that are down.
Fixes issue #20926.
|
|
|
|
|
|
This is safe now we are choosing 200 fallbacks.
Closes ticket 20912.
|
|
This allows 73% of clients to bootstrap in the first 5 seconds without
contacting an authority.
Part of #18828.
|
|
7 days is a tradeoff between the expected time between major Tor releases,
which is 6 months, and the number of relays with enough stability.
Relays whose OnionOO stability timer is reset on restart by bug #18050
should upgrade to Tor 0.2.8.7 or later, which has a fix for this issue.
Closes ticket #20880; maintains short-term fix in e220214 in tor-0.2.8.2-alpha.
|
|
|
|
Part of #20539, based on #20501.
|
|
Part of #20539, based on #20509.
|
|
Closes issue #20882.
|
|
Closes ticket #20881.
|
|
And make it clear that updateFallbackDirs.py outputs bandwidth in
megabytes per second.
Closes #20878.
|
|
Closes ticket #20877.
|
|
If we manually remove fallbacks in C by adding '/*' and '*/' on separate
lines, stem still parses them as being present, because it only looks at
the start of a line.
Add a comment to this effect in the generated source code.
|
|
|
|
|
|
No behavioural change
|
|
Log a notice just before the script is about to perform a
potentially time-consuming operation
Clarify the warning when py2-ipaddress isn't found
Make log levels more consistent
No behavioural change (just logging)
|
|
|
|
As well as the existing reports of IPv6 address additions or removals,
the script now warns when keys change but IPv4:ORPort or
IPv6:IPv6ORPort remain the same.
Existing checks for other whitelist detail changes have also
been re-worded and upgraded to warnings.
This makes it easier for changes to be identified so operators can
be contacted to confirm whether the change is stable.
|
|
Use IP address, effective family, and contact info to
discover and limit fallbacks to one per operator.
Also analyse netblock, ports, IP version, and Exit flag,
and print the results. Don't exclude any fallbacks from
the list because of netblocks, ports, IP version, or
Exit flag.
|
|
When creating the list of fallbacks for a release:
* don't output fallback name and contact
* sort fallbacks by fingerprint
|