summaryrefslogtreecommitdiff
path: root/changes
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2012-08-03 12:04:36 -0400
committerNick Mathewson <nickm@torproject.org>2012-08-03 12:04:36 -0400
commitaa584fd3a3888de836bb5c23b7372676c557a735 (patch)
tree8ed451f1492d9207f435eeeffeefc6ca7c7b88bb /changes
parent860c4fc81166568f2909708c455ca6a70d81a2f8 (diff)
parent93be3a8822ae791cc8adb78ea7d7e76e4c10db41 (diff)
downloadtor-aa584fd3a3888de836bb5c23b7372676c557a735.tar.gz
tor-aa584fd3a3888de836bb5c23b7372676c557a735.zip
Merge remote-tracking branch 'origin/maint-0.2.3'
Diffstat (limited to 'changes')
-rw-r--r--changes/pathsel-BUGGY-a14
1 files changed, 14 insertions, 0 deletions
diff --git a/changes/pathsel-BUGGY-a b/changes/pathsel-BUGGY-a
new file mode 100644
index 0000000000..2e642c7953
--- /dev/null
+++ b/changes/pathsel-BUGGY-a
@@ -0,0 +1,14 @@
+ o Security fixes:
+
+ - Try to leak less information about what relays a client is
+ choosing to a side-channel attacker. Previously, a Tor client
+ would stop iterating through the list of available relays as
+ soon as it had chosen one, thus finishing a little earlier
+ when it picked a router earlier in the list. If an attacker
+ can recover this timing information (nontrivial but not
+ proven to be impossible), they could learn some coarse-
+ grained information about which relays a client was picking
+ (middle nodes in particular are likelier to be affected than
+ exits). The timing attack might be mitigated by other factors
+ (see bug #6537 for some discussion), but it's best not to
+ take chances. Fixes bug 6537; bugfix on 0.0.8rc1.