diff options
author | Nick Mathewson <nickm@torproject.org> | 2020-07-22 15:20:41 -0400 |
---|---|---|
committer | Nick Mathewson <nickm@torproject.org> | 2020-07-22 15:21:56 -0400 |
commit | ceb6585a4bc2beadde2fb194395711e72ee8559d (patch) | |
tree | 49e2c28d001d9f11daf0b2c60df768b912115794 /changes | |
parent | c9751e26119e375fcbc74107e89958957c00ee5e (diff) | |
download | tor-ceb6585a4bc2beadde2fb194395711e72ee8559d.tar.gz tor-ceb6585a4bc2beadde2fb194395711e72ee8559d.zip |
Treat all extorport connections with un-set addresses as remote
Without this fix, if an PT forgets to send a USERADDR command, that
results in a connection getting treated as local for the purposes of
rate-limiting.
If the PT _does_ use USERADDR, we still believe it.
Closes ticket 33747.
Diffstat (limited to 'changes')
-rw-r--r-- | changes/ticket33747 | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/changes/ticket33747 b/changes/ticket33747 new file mode 100644 index 0000000000..57c72e9d0a --- /dev/null +++ b/changes/ticket33747 @@ -0,0 +1,7 @@ + o Minor bugfixes (rate limiting, bridges, pluggable transports): + - On a bridge, treat all connections from an ExtORPort as remote + by default for the purposes of rate-limiting. Previously, + bridges would treat the connection as local unless they explicitly + received a "USERADDR" command. ExtORPort connections still + count as local if there is a USERADDR command with an explicit local + address. Fixes bug 33747; bugfix on 0.2.5.1-alpha. |