aboutsummaryrefslogtreecommitdiff
path: root/src/or/router.h
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2012-12-04 15:58:18 -0500
committerNick Mathewson <nickm@torproject.org>2013-01-02 14:11:14 -0500
commit5b3dd1610cf2147509167332bf298fc821e6a102 (patch)
tree081d16b883ba26f1b606656687470184676fb090 /src/or/router.h
parent6c883bc6384b3260d791e407b42ffcabb8276beb (diff)
downloadtor-5b3dd1610cf2147509167332bf298fc821e6a102.tar.gz
tor-5b3dd1610cf2147509167332bf298fc821e6a102.zip
Wrangle curve25519 onion keys: generate, store, load, publish, republish
Here we try to handle curve25519 onion keys from generating them, loading and storing them, publishing them in our descriptors, putting them in microdescriptors, and so on. This commit is untested and probably buggy like whoa
Diffstat (limited to 'src/or/router.h')
-rw-r--r--src/or/router.h5
1 files changed, 5 insertions, 0 deletions
diff --git a/src/or/router.h b/src/or/router.h
index b641c1cc6a..85c7d351d1 100644
--- a/src/or/router.h
+++ b/src/or/router.h
@@ -30,6 +30,11 @@ crypto_pk_t *init_key_from_file(const char *fname, int generate,
int severity);
void v3_authority_check_key_expiry(void);
+#ifdef CURVE25519_ENABLED
+di_digest256_map_t *construct_ntor_key_map(void);
+void ntor_key_map_free(di_digest256_map_t *map);
+#endif
+
int router_initialize_tls_context(void);
int init_keys(void);