summaryrefslogtreecommitdiff
path: root/changes/bug2511
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2011-02-08 08:08:47 -0500
committerRoger Dingledine <arma@torproject.org>2011-02-08 08:08:47 -0500
commit9a1a96ba0947e1c9b0e43aef6600b0d083586cf5 (patch)
treec936dfbd9b091e9ec6fa7c4a6b50957ed6cebdec /changes/bug2511
parent54ccc80a4a740c175f279d00dc5441c673b0263c (diff)
downloadtor-9a1a96ba0947e1c9b0e43aef6600b0d083586cf5.tar.gz
tor-9a1a96ba0947e1c9b0e43aef6600b0d083586cf5.zip
don't use old non-configured bridges (bug 2511)
Diffstat (limited to 'changes/bug2511')
-rw-r--r--changes/bug25116
1 files changed, 6 insertions, 0 deletions
diff --git a/changes/bug2511 b/changes/bug2511
new file mode 100644
index 0000000000..a27696a5ff
--- /dev/null
+++ b/changes/bug2511
@@ -0,0 +1,6 @@
+ o Major bugfixes:
+ - If you configured Tor to use bridge A, and then quit and
+ configured Tor to use bridge B instead, it would happily continue
+ to use bridge A if it's still reachable. While this behavior is
+ a feature if your goal is connectivity, in some scenarios it's a
+ dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.