Age | Commit message (Collapse) | Author |
|
|
|
Closes #19307.
|
|
|
|
Part of 21283.
|
|
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.
|
|
|
|
|
|
|
|
(And its contact email address no longer works.)
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
Closes ticket 21096.
|
|
Found using flake8 which gave the following output;
lintChanges.py:10:13: E225 missing whitespace around operator
lintChanges.py:25:1: E302 expected 2 blank lines, found 1
lintChanges.py:46:5: F841 local variable 'lines' is assigned to but never used
lintChanges.py:52:32: E228 missing whitespace around modulo operator
lintChanges.py:53:11: E201 whitespace after '('
lintChanges.py:56:41: E228 missing whitespace around modulo operator
Part of ticket 21096.
|
|
These updates were made after the December 2016 list was created.
|
|
|
|
Based on:
* fallback directory mirror checks,
* operator emails and tickets, both before and after the Dec 2016 emails:
https://lists.torproject.org/pipermail/tor-relays/2016-December/011113.html
https://lists.torproject.org/pipermail/tor-relays/2016-December/011330.html
|
|
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.
|
|
|
|
These updates assume that the changes were intentional and permanent.
The operators were emailed to confirm.
|
|
Part of #20539, based on #20501.
|
|
Part of #20539, based on #20509.
|
|
Update fallback whitelist and blacklist based on:
* pre-0.2.9 checks
* operator opt-ins and opt-outs, via emails and tickets
|
|
Closes issue #20882.
|
|
Closes ticket #20881.
|
|
And make it clear that updateFallbackDirs.py outputs bandwidth in
megabytes per second.
Closes #20878.
|
|
Closes ticket #20877.
|
|
Substitutions were made using `sed -e 's/print/msg/g'`.
|
|
|
|
|
|
Without the 'my' keyword the variables are global and Perl requires
global symbols to include an explicit package name.
|
|
|
|
|
|
The functions it warns about are:
assert, memcmp, strcat, strcpy, sprintf, malloc, free, realloc,
strdup, strndup, calloc.
Also, fix a few lingering instances of these in the code. Use other
conventions to indicate _intended_ use of assert and
malloc/realloc/etc.
|
|
Previously we would give a warning because we didn't say "Fixes bug
Foo" on these.
|
|
|
|
The fallback was added in 0.2.8.2-alpha.
|
|
Only some very ancient distributions don't ship with Libevent 2 anymore,
even the oldest supported Ubuntu LTS version has it. This allows us to
get rid of a lot of compat code.
|