| Age | Commit message (Collapse) | Author |
|---|
|
Without this change, if we have a working bridge, and we add a new bridge,
we will schedule the fetch attempt for that new bridge descriptor for
three hours(!) in the future.
This change is especially needed because of bug #40396, where if you have
one working bridge and one bridge whose descriptor you haven't fetched
yet, your Tor will stall until you have successfully fetched that new
descriptor -- in this case for hours.
In the old design, we would put off all further bridge descriptor fetches
once we had any working bridge descriptor. In this new design, we make the
decision per bridge based on whether we successfully got *its* descriptor.
To make this work, we need to also call learned_bridge_descriptor() every
time we get a bridge descriptor, not just when it's a novel descriptor.
Fixes bug 40396.
Also happens to fix bug 40495 (redundant descriptor fetches for every
bridge) since now we delay fetches once we succeed.
A side effect of this change is that if we have any configured bridges
that *aren't* working, we will keep trying to fetch their descriptors
on the modern directory retry schedule -- every couple of seconds for
the first half minute, then backing off after that -- which is a lot
faster than before.
|
|
|
|
Closes #40448.
|
|
|
|
Signed-off-by: David Goulet <dgoulet@torproject.org>
|
|
Closes #40469
Signed-off-by: David Goulet <dgoulet@torproject.org>
|
|
|
|
Add few missing periods, convert tabs to spaces.
No new significant content added.
Signed-off-by: skaluzka <skaluzka@protonmail.com>
|
|
|
|
Move the options into the DDoS section with a series of explanations.
Closes #40456
Signed-off-by: David Goulet <dgoulet@torproject.org>
|
|
Remove all unnecessary ";" characters at the end of several lines.
Align all indentations to 4 spaces.
Update console messages related to XML_CATALOG_FILES and
.bashrc file.
Signed-off-by: skaluzka <skaluzka@protonmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
Closes #33742
|
|
|
|
This patch is part of a series of patches where we try to change our
primary branch name of tor.git from master to main.
See: tpo/core/team#2
|
|
|
|
|
|
Closes #40346
Signed-off-by: David Goulet <dgoulet@torproject.org>
|
|
|
|
patch from cypherpunks; closes #40323
|
|
Fixes bug #40296 .
|
|
Patch from 'cypherpunks'. Closes #40331.
|
|
This incorporates a suggestion from cypherpunks on #40321
Closes #40321.
|
|
|
|
(If you need to do this in an older version you can just set
DormantClientTimeout to something huge.)
Closes #40228.
|
|
This option changes the time for which a bandwidth measurement period
must have been in progress before we include it when reporting our
observed bandwidth in our descriptors. Without this option, we only
consider a time period towards our maximum if it has been running
for a full day. Obviously, that's unacceptable for testing
networks, where we'd like to get results as soon as possible.
For non-testing networks, I've put a (somewhat arbitrary) 2-hour
minimum on the option, since there are traffic analysis concerns
with immediate reporting here.
Closes #40337.
|
|
|
|
Fixes bug #40256; bugfix on 0.2.9.4-alpha.
|
|
|
|
|
|
Signed-off-by: David Goulet <dgoulet@torproject.org>
|
|
This is a new detection type which is that a relay can now control the rate of
client connections from a single address.
The mechanism is pretty simple, if the rate/burst is reached, the address is
marked for a period of time and any connection from that address is denied.
Closes #40253
Signed-off-by: David Goulet <dgoulet@torproject.org>
|
|
Signed-off-by: David Goulet <dgoulet@torproject.org>
|
|
|
|
|
|
Document !badexit, and improve the documentation for !invalid.
Closes #40188.
|
|
|
|
Typos found with codespell.
Please keep in mind that this should have impact on actual code
and must be carefully evaluated:
src/core/or/lttng_circuit.inc
- ctf_enum_value("CONTROLER", CIRCUIT_PURPOSE_CONTROLLER)
+ ctf_enum_value("CONTROLLER", CIRCUIT_PURPOSE_CONTROLLER)
|
|
Signed-off-by: David Goulet <dgoulet@torproject.org>
|
|
|
|
Make it possible to specify multiple ConsensusParams torrc
lines.
Now directory authority operators can for example put the
main ConsensusParams config in one torrc file and then add to it
from a different torrc file.
Closes ticket 40164.
|
|
Affected entries are: EntryNodes, ExcludeNodes, ExcludeExitNodes,
ExitNodes, MiddleNodes, HSLayer2Nodes and HSLayer3Nodes.
|
|
|
|
|
|
|
|
We've been using it for years, and it seems to work just fine. This
patch removes the option and its network parameter.
Part of #40139
|
