aboutsummaryrefslogtreecommitdiff
path: root/src/or/or.h
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2016-11-21 17:23:25 -0500
committerNick Mathewson <nickm@torproject.org>2016-11-30 14:42:53 -0500
commitdbbaa515183e250e20c40fa7b4c00df9487058fa (patch)
treead7047ded85f1c231ff158e6aad8201824a72148 /src/or/or.h
parentde617a471442342fc2abafdde4e250fd31eb45ac (diff)
downloadtor-dbbaa515183e250e20c40fa7b4c00df9487058fa.tar.gz
tor-dbbaa515183e250e20c40fa7b4c00df9487058fa.zip
Use the new guard notification/selection APIs throughout Tor
This patch doesn't cover every case; omitted cases are marked with "XXXX prop271", as usual. It leaves both the old interface and the new interface for guard status notification, since they don't actually work in the same way: the new API wants to be told when a circuit has failed or succeeded, whereas the old API wants to know when a channel has failed or succeeded. I ran into some trouble with directory guard stuff, since when we pick the directory guard, we don't actually have a circuit to associate it with. I solved that by allowing guard states to be associated with directory connections, not just circuits.
Diffstat (limited to 'src/or/or.h')
-rw-r--r--src/or/or.h4
1 files changed, 4 insertions, 0 deletions
diff --git a/src/or/or.h b/src/or/or.h
index c8f39f90d9..8b9ede3607 100644
--- a/src/or/or.h
+++ b/src/or/or.h
@@ -1786,6 +1786,10 @@ typedef struct dir_connection_t {
/** What rendezvous service are we querying for? */
rend_data_t *rend_data;
+ /** If this is a one-hop connection, tracks the state of the directory guard
+ * for this connection (if any). */
+ struct circuit_guard_state_t *guard_state;
+
char identity_digest[DIGEST_LEN]; /**< Hash of the public RSA key for
* the directory server's signing key. */