challenger

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

commit 285c251000766ea86de0f71f10c70c3ac0492292
parent 2aa68d300255e551558c423841727ef88b9494f4
Author: Christian Grothoff <christian@grothoff.org>
Date:   Thu, 17 Apr 2025 21:41:47 +0200

allow pin transmissions without address changes in case we had a read_only address

Diffstat:
Msrc/challenger/challenger-httpd_challenge.c | 2--
Msrc/challenger/challenger-httpd_solve.c | 4++--
Msrc/challengerdb/challenger-0001.sql | 2+-
3 files changed, 3 insertions(+), 5 deletions(-)

diff --git a/src/challenger/challenger-httpd_challenge.c b/src/challenger/challenger-httpd_challenge.c @@ -907,8 +907,6 @@ CH_handler_challenge (struct CH_HandlerContext *hc, args = GNUNET_JSON_PACK ( GNUNET_JSON_pack_uint64 ("attempts_left", bc->pin_attempts_left), - GNUNET_JSON_pack_string ("nonce", - hc->path), GNUNET_JSON_pack_string ("type", "created"), GNUNET_JSON_pack_object_incref ("address", diff --git a/src/challenger/challenger-httpd_solve.c b/src/challenger/challenger-httpd_solve.c @@ -335,11 +335,11 @@ CH_handler_solve (struct CH_HandlerContext *hc, GNUNET_log (GNUNET_ERROR_TYPE_INFO, "Invalid PIN supplied\n"); details = GNUNET_JSON_PACK ( + GNUNET_JSON_pack_string ("type", + "pending"), TALER_JSON_pack_ec (TALER_EC_CHALLENGER_INVALID_PIN), GNUNET_JSON_pack_uint64 ("addresses_left", bc->addr_left), - GNUNET_JSON_pack_string ("type", - "pending"), GNUNET_JSON_pack_uint64 ("pin_transmissions_left", bc->pin_transmissions_left), GNUNET_JSON_pack_uint64 ("auth_attempts_left", diff --git a/src/challengerdb/challenger-0001.sql b/src/challengerdb/challenger-0001.sql @@ -53,7 +53,7 @@ CREATE TABLE IF NOT EXISTS validations ,last_tx_time INT8 NOT NULL DEFAULT (0) ,address_attempts_left INT4 DEFAULT(3) ,last_pin INT4 - ,pin_transmissions_left INT4 DEFAULT(0) + ,pin_transmissions_left INT4 DEFAULT(3) ,auth_attempts_left INT4 DEFAULT(0) ,address VARCHAR ,client_scope VARCHAR