mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-11-11 05:33:47 +01:00
Increase OPE_INPUT_MAX.
This commit is contained in:
parent
3a45f6ffe9
commit
34a5eb5904
@ -13,8 +13,18 @@
|
|||||||
/** Length of OPE key, in bytes. */
|
/** Length of OPE key, in bytes. */
|
||||||
#define OPE_KEY_LEN 32
|
#define OPE_KEY_LEN 32
|
||||||
|
|
||||||
/** Largest value that can be passed to crypto_ope_encrypt() */
|
/** Largest value that can be passed to crypto_ope_encrypt().
|
||||||
#define OPE_INPUT_MAX 131072
|
*
|
||||||
|
* Expressed as 2^18 because the OPE system prefers powers of two.
|
||||||
|
*
|
||||||
|
* The current max value stands for about 70 hours. The rationale here is as
|
||||||
|
* follows: The rev counter is the time of seconds since the start of an SRV
|
||||||
|
* period. SRVs are useful for about 48 hours (that's how long they stick
|
||||||
|
* around on the consensus). Let's also add 12 hours of drift for clock skewed
|
||||||
|
* services that might be using an old consensus and we arrive to 60
|
||||||
|
* hours. The max value should be beyond that.
|
||||||
|
*/
|
||||||
|
#define OPE_INPUT_MAX (1<<18)
|
||||||
|
|
||||||
typedef struct crypto_ope_c crypto_ope_t;
|
typedef struct crypto_ope_c crypto_ope_t;
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user