challenger

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

commit 8fde6e32ee9d8ab0bb477b4b5024337e479654f8
parent f31b4b06ff0f7ae47676eee8879ca13d7046bd58
Author: Christian Grothoff <christian@grothoff.org>
Date:   Thu,  6 Aug 2026 15:30:10 +0200

do not use ro after old_address decref

Diffstat:
Msrc/challenger/challenger-httpd_challenge.c | 4++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/challenger/challenger-httpd_challenge.c b/src/challenger/challenger-httpd_challenge.c @@ -967,12 +967,12 @@ CH_handler_challenge (struct CH_HandlerContext *hc, TALER_EC_CHALLENGER_CLIENT_FORBIDDEN_READ_ONLY, NULL); } - json_decref (old_address); - if (ro) + if (NULL != ro) GNUNET_assert (0 == json_object_set (bc->address, "read_only", ro)); + json_decref (old_address); qs = CHALLENGERDB_do_challenge_address (CH_context, &bc->nonce,