summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMicah Elizabeth Scott <beth@torproject.org>2023-03-21 12:56:10 -0700
committerMicah Elizabeth Scott <beth@torproject.org>2023-05-10 07:38:29 -0700
commitac29c7209dbdaf0d317f1c4eb67d5e330386552b (patch)
tree81d56c553348e7445df56cdcd0131b695f1b9a51
parent6a0809c4e301f302367c751c5c11ff470bcf7388 (diff)
downloadtor-ac29c7209dbdaf0d317f1c4eb67d5e330386552b.tar.gz
tor-ac29c7209dbdaf0d317f1c4eb67d5e330386552b.zip
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>
-rw-r--r--src/feature/hs/hs_client.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/feature/hs/hs_client.c b/src/feature/hs/hs_client.c
index 6a404395ea..2a620da953 100644
--- 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.