summaryrefslogtreecommitdiff
path: root/changes
diff options
context:
space:
mode:
authorDavid Goulet <dgoulet@torproject.org>2020-03-10 14:45:13 -0400
committerDavid Goulet <dgoulet@torproject.org>2020-03-10 14:45:13 -0400
commit894ff2dc8422cb86312c512698acd76476224f87 (patch)
tree6be4ed48b020021d68cb54d10ec61b7382382fef /changes
parentb9c7c61ea5233854ff83257a8bc530b7e0a50351 (diff)
downloadtor-894ff2dc8422cb86312c512698acd76476224f87.tar.gz
tor-894ff2dc8422cb86312c512698acd76476224f87.zip
dos: Pass transport name on new client connection
For a bridge configured with a pluggable transport, the transport name is used, with the IP address, for the GeoIP client cache entry. However, the DoS subsystem was not aware of it and always passing NULL when doing a lookup into the GeoIP cache. This resulted in bridges with a PT are never able to apply DoS defenses for newly created connections. Fixes #33491 Signed-off-by: David Goulet <dgoulet@torproject.org>
Diffstat (limited to 'changes')
-rw-r--r--changes/ticket334916
1 files changed, 6 insertions, 0 deletions
diff --git a/changes/ticket33491 b/changes/ticket33491
new file mode 100644
index 0000000000..595ea863ea
--- /dev/null
+++ b/changes/ticket33491
@@ -0,0 +1,6 @@
+ o Major bugfixes (DoS defenses, bridges, pluggable transport):
+ - DoS subsystem was not given the transport name of the client connection
+ when tor is a bridge and thus failing to find the GeoIP cache entry for
+ that client address. This resulted in failing to apply DoS defenses on
+ bridges with a pluggable transport. Fixes bug 33491; bugfix on
+ 0.3.3.2-alpha.