diff options
author | Nick Mathewson <nickm@torproject.org> | 2013-02-04 12:50:01 -0500 |
---|---|---|
committer | Nick Mathewson <nickm@torproject.org> | 2013-02-07 14:09:01 -0500 |
commit | 266419d244c1a4795407479693b016c5a8b5da96 (patch) | |
tree | cb5c0b8a9aab066209f81bb8b80cb1e7c3719929 /changes | |
parent | 898f2d7c278442d2c4fbdf0126eaa406d503d088 (diff) | |
download | tor-266419d244c1a4795407479693b016c5a8b5da96.tar tor-266419d244c1a4795407479693b016c5a8b5da96.tar.gz |
Tolerate curve25519 backends where the high bit of the pk isn't ignored
Right now, all our curve25519 backends ignore the high bit of the
public key. But possibly, others could treat the high bit of the
public key as encoding out-of-bounds values, or as something to be
preserved. This could be used to distinguish clients with different
backends, at the cost of killing a circuit.
As a workaround, let's just clear the high bit of each public key
indiscriminately before we use it. Fix for bug 8121, reported by
rransom. Bugfix on 0.2.4.8-alpha.
Diffstat (limited to 'changes')
-rw-r--r-- | changes/bug8121 | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/changes/bug8121 b/changes/bug8121 new file mode 100644 index 000000000..60cba7284 --- /dev/null +++ b/changes/bug8121 @@ -0,0 +1,7 @@ + o Minor features: + - Clear the high bit on curve25519 public keys before passing them to + our backend, in case we ever wind up using a backend that doesn't do + so itself. If we used such a backend, and *didn't* clear the high bit, + we could wind up in a situation where users with such backends would + be distinguishable from users without. Fix for bug 8121; bugfix on + 0.2.4.8-alpha. |