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>

diff --git a/src/feature/hs/hs_client.c b/src/feature/hs/hs_client.c
index 6a404395ea6b3d0cb150c3bd1acd7a9cb9d0cb9e..2a620da95392552696eb72adf5310b83bcd3e13a 100644 (file)
--- a/src/feature/hs/hs_client.c
+++ b/src/feature/hs/hs_client.c
@@ -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
  * 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
  * circuit identifier with the needed key material for the e2e encryption.