summaryrefslogtreecommitdiff
path: root/src/or/router.h
diff options
context:
space:
mode:
authorGeorge Kadianakis <desnacked@gmail.com>2011-11-24 06:40:02 +0100
committerGeorge Kadianakis <desnacked@gmail.com>2011-11-25 18:15:26 +0100
commite3cee8bc2e8df6b39a4122829649e3f9ab920aa6 (patch)
tree3c0614eaebce2f2f9f5a63939f1b1b5afac9d45e /src/or/router.h
parente2a189053dd93ba94d13035fff5008fcdefa8eca (diff)
downloadtor-e3cee8bc2e8df6b39a4122829649e3f9ab920aa6.tar.gz
tor-e3cee8bc2e8df6b39a4122829649e3f9ab920aa6.zip
Simply initialize TLS context if DynamicDHGroups change.
We used to do init_keys() if DynamicDHGroups changed after a HUP, so that the dynamic DH modulus was stored on the disk. Since we are now doing dynamic DH modulus storing in crypto.c, we can simply initialize the TLS context and be good with it. Introduce a new function router_initialize_tls_context() which initializes the TLS context and use it appropriately.
Diffstat (limited to 'src/or/router.h')
-rw-r--r--src/or/router.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/or/router.h b/src/or/router.h
index f9d156cb09..68eadbf4c2 100644
--- a/src/or/router.h
+++ b/src/or/router.h
@@ -30,6 +30,7 @@ crypto_pk_env_t *init_key_from_file(const char *fname, int generate,
int severity);
void v3_authority_check_key_expiry(void);
+int router_initialize_tls_context(void);
int init_keys(void);
int check_whether_orport_reachable(void);