aboutsummaryrefslogtreecommitdiff
path: root/changes/pathsel-BUGGY-a
diff options
context:
space:
mode:
authorRobert Ransom <rransom.8774@gmail.com>2012-06-14 17:15:54 +0000
committerNick Mathewson <nickm@torproject.org>2012-08-03 11:49:51 -0400
commit308f6dad20675c42b29862f4269ad1fbfb00dc9a (patch)
tree4c1e39fdfdafc9b705cef91549f08f7e3ca008db /changes/pathsel-BUGGY-a
parent55f635745afacefffdaafc72cc176ca7ab817546 (diff)
downloadtor-308f6dad20675c42b29862f4269ad1fbfb00dc9a.tar.gz
tor-308f6dad20675c42b29862f4269ad1fbfb00dc9a.zip
Mitigate a side-channel leak of which relays Tor chooses for a circuit
Tor's and OpenSSL's current design guarantee that there are other leaks, but this one is likely to be more easily exploitable, and is easy to fix.
Diffstat (limited to 'changes/pathsel-BUGGY-a')
-rw-r--r--changes/pathsel-BUGGY-a12
1 files changed, 12 insertions, 0 deletions
diff --git a/changes/pathsel-BUGGY-a b/changes/pathsel-BUGGY-a
new file mode 100644
index 0000000000..cad2af5c0d
--- /dev/null
+++ b/changes/pathsel-BUGGY-a
@@ -0,0 +1,12 @@
+ 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 leaking information about which
+ relays it picked for a circuit to a timing attack. (Tor is
+ likely to still leak information about which relays it has
+ chosen for a circuit to other processes on the same computer,
+ through e.g. which cache lines it loads while building the
+ circuit.)
+