This is an automated email from the git hooks/post-receive script. dgoulet pushed a commit to branch main in repository tor. commit ac29c7209dbdaf0d317f1c4eb67d5e330386552b Author: Micah Elizabeth Scott <beth@torproject.org> AuthorDate: Tue Mar 21 12:56:10 2023 -0700 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> --- src/feature/hs/hs_client.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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. -- To stop receiving notification emails like this one, please contact the administrator of this repository.