diff options
| author | teor (Tim Wilson-Brown) <teor2345@gmail.com> | 2016-07-07 12:58:47 +1000 |
|---|---|---|
| committer | teor (Tim Wilson-Brown) <teor2345@gmail.com> | 2016-07-15 09:55:49 +1000 |
| commit | 579a80d4ae54ec03fd9b02c4a125b2943770c85d (patch) | |
| tree | 816ee00f3ed7dff2fe350d1a2fcb49469baea1ac /changes/reject-tap | |
| parent | a76d528bec970e500d3339d9e0f253bded17c338 (diff) | |
| download | tor-579a80d4ae54ec03fd9b02c4a125b2943770c85d.tar.gz tor-579a80d4ae54ec03fd9b02c4a125b2943770c85d.zip | |
Clients avoid choosing nodes that can't do ntor
If we know a node's version, and it can't do ntor, consider it not running.
If we have a node's descriptor, and it doesn't have a valid ntor key,
consider it not running.
Refactor these checks so they're consistent between authorities and clients.
Diffstat (limited to 'changes/reject-tap')
| -rw-r--r-- | changes/reject-tap | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/changes/reject-tap b/changes/reject-tap index 77ca63b46e..75800184fd 100644 --- a/changes/reject-tap +++ b/changes/reject-tap @@ -7,4 +7,7 @@ instead, they check specifically for an ntor key. - Clients avoid downloading a descriptor if the relay version is too old to support ntor. + - Client code ignores nodes without ntor keys: they will not be + selected during circuit-building, or as guards, or as directory + mirrors, or as introduction or rendezvous points. Fixes bug 19163; bugfix on 0.2.4.18-rc. |