mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-11-24 04:13:28 +01:00
hs_pow: bump client-side effort limit from 500 to 10000
500 was quite low, but this limit was helpful when the suggested-effort estimation algorithm was likely to give us large abrupt increases. Now that this should be fixed, let's allow spending a bit more time on the client puzzles if it's actually necessary. Solving a puzzle with effort=10000 usually completes within a minute on my old x86_64 machine. We may want to fine tune this further, and it should probably be made into a config option. Signed-off-by: Micah Elizabeth Scott <beth@torproject.org>
This commit is contained in:
parent
6a0809c4e3
commit
ac29c7209d
@ -655,7 +655,7 @@ send_introduce1(origin_circuit_t *intro_circ,
|
|||||||
|
|
||||||
/** Set a client-side cap on the highest effort of PoW we will try to
|
/** Set a client-side cap on the highest effort of PoW we will try to
|
||||||
* tackle. If asked for higher, we solve it at this cap. */
|
* tackle. If asked for higher, we solve it at this cap. */
|
||||||
#define CLIENT_MAX_POW_EFFORT 500
|
#define CLIENT_MAX_POW_EFFORT 10000
|
||||||
|
|
||||||
/** Send an INTRODUCE1 cell along the intro circuit and populate the rend
|
/** Send an INTRODUCE1 cell along the intro circuit and populate the rend
|
||||||
* circuit identifier with the needed key material for the e2e encryption.
|
* circuit identifier with the needed key material for the e2e encryption.
|
||||||
|
Loading…
Reference in New Issue
Block a user