summaryrefslogtreecommitdiff
path: root/src/or/or.h
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2017-09-11 10:00:11 -0400
committerNick Mathewson <nickm@torproject.org>2017-09-11 10:00:11 -0400
commit3124c921e7af15548b8b16d5f239bfdcd178b2ca (patch)
treebc58c6a9f9b761672ce00d5e19bc5fce3bbe02fa /src/or/or.h
parent362bc880b1c4bbccba8698b872c16fc6a6da168e (diff)
downloadtor-3124c921e7af15548b8b16d5f239bfdcd178b2ca.tar.gz
tor-3124c921e7af15548b8b16d5f239bfdcd178b2ca.zip
Split the behavior of node_supports_ed25519_link_authentication().
Before, this function meant "can we connect to this node and authenticate it using its ed25519 key?" Now it can additionally mean, "when somebody else connects to this node, do we expect that they can authenticate using the node's ed25519 key"? This change lets us future-proof our link authentication a bit. Closes ticket 20895. No backport needed, since ed25519 link authentication support has not been in any LTS release yet, and existing releases with it should be obsolete before any releases without support for linkauth=3 are released.
Diffstat (limited to 'src/or/or.h')
-rw-r--r--src/or/or.h8
1 files changed, 6 insertions, 2 deletions
diff --git a/src/or/or.h b/src/or/or.h
index 161d80ed96..8e1d15b8cb 100644
--- a/src/or/or.h
+++ b/src/or/or.h
@@ -2316,8 +2316,12 @@ typedef struct routerstatus_t {
unsigned int supports_extend2_cells:1;
/** True iff this router has a protocol list that allows it to negotiate
- * ed25519 identity keys on a link handshake. */
- unsigned int supports_ed25519_link_handshake:1;
+ * ed25519 identity keys on a link handshake with us. */
+ unsigned int supports_ed25519_link_handshake_compat:1;
+
+ /** True iff this router has a protocol list that allows it to negotiate
+ * ed25519 identity keys on a link handshake, at all. */
+ unsigned int supports_ed25519_link_handshake_any:1;
/** True iff this router has a protocol list that allows it to be an
* introduction point supporting ed25519 authentication key which is part of