aboutsummaryrefslogtreecommitdiff
path: root/src/or/or.h
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2015-03-01 14:36:40 +0100
committerNick Mathewson <nickm@torproject.org>2015-05-28 10:42:30 -0400
commit57189acd6f6b56a419d63a7acb012a9b8abac319 (patch)
treecae61ade268b8e599ca4299a73b403203f15a584 /src/or/or.h
parent64450c5f775c6453568c5ac218669ff0525dc232 (diff)
downloadtor-57189acd6f6b56a419d63a7acb012a9b8abac319.tar.gz
tor-57189acd6f6b56a419d63a7acb012a9b8abac319.zip
# This is a combination of 2 commits.
# The first commit's message is: Regenerate ed25519 keys when they will expire soon. Also, have testing-level options to set the lifetimes and expiration-tolerances of all key types, plus a non-testing-level option to set the lifetime of any auto-generated signing key. # The 2nd commit message will be skipped: # fixup! Regenerate ed25519 keys when they will expire soon.
Diffstat (limited to 'src/or/or.h')
-rw-r--r--src/or/or.h15
1 files changed, 15 insertions, 0 deletions
diff --git a/src/or/or.h b/src/or/or.h
index b07a596d2e..d45e19ad8d 100644
--- a/src/or/or.h
+++ b/src/or/or.h
@@ -4261,6 +4261,21 @@ typedef struct {
* XXXX Eventually, the default will be 0. */
int ExitRelay;
+
+ /** For how long (seconds) do we declare our singning keys to be valid? */
+ int SigningKeyLifetime;
+ /** For how long (seconds) do we declare our link keys to be valid? */
+ int TestingLinkKeyLifetime;
+ /** For how long (seconds) do we declare our auth keys to be valid? */
+ int TestingAuthKeyLifetime;
+
+ /** How long before signing keys expire will we try to make a new one? */
+ int TestingSigningKeySlop;
+ /** How long before link keys expire will we try to make a new one? */
+ int TestingLinkKeySlop;
+ /** How long before auth keys expire will we try to make a new one? */
+ int TestingAuthKeySlop;
+
} or_options_t;
/** Persistent state for an onion router, as saved to disk. */