challenger

OAuth 2.0-based authentication service that validates user can receive messages at a certain address
Log | Files | Refs | Submodules | README | LICENSE

commit 1418e47826457b8bf11c8d5464bce0126a06e6eb
parent 5c4dd7599cb7fa7f4814fd51a39d6bd62078c06a
Author: Christian Grothoff <christian@grothoff.org>
Date:   Mon,  6 Jul 2026 10:44:46 +0200

cleaner to do FOR UPDATE as we will UPDATE later

Diffstat:
Msrc/challengerdb/challenger_do_challenge_set_address_and_pin.sql | 3++-
Msrc/challengerdb/challenger_do_validate_and_solve_pin.sql | 3++-
2 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/src/challengerdb/challenger_do_challenge_set_address_and_pin.sql b/src/challengerdb/challenger_do_challenge_set_address_and_pin.sql @@ -49,7 +49,8 @@ SELECT address ,client_state INTO my_status FROM validations - WHERE nonce=in_nonce; + WHERE nonce=in_nonce + FOR UPDATE; IF NOT FOUND THEN diff --git a/src/challengerdb/challenger_do_validate_and_solve_pin.sql b/src/challengerdb/challenger_do_validate_and_solve_pin.sql @@ -40,7 +40,8 @@ SELECT auth_attempts_left ,client_state INTO my_status FROM validations - WHERE nonce=in_nonce; + WHERE nonce=in_nonce + FOR UPDATE; IF NOT FOUND THEN