challenger

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

commit 9767a86c98bd83e209b688919854a874e39534ca
parent 690ce695415810012382f371fb11ab5f872bdeac
Author: Christian Grothoff <christian@grothoff.org>
Date:   Wed,  6 Mar 2024 17:20:41 +0100

-allow NULL

Diffstat:
Msrc/challenger/challenger-httpd_authorize.c | 5+++--
1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/src/challenger/challenger-httpd_authorize.c b/src/challenger/challenger-httpd_authorize.c @@ -207,8 +207,9 @@ CH_handler_authorize (struct CH_HandlerContext *hc, "enter-%s-form", CH_address_type); args = GNUNET_JSON_PACK ( - GNUNET_JSON_pack_object_incref ("restrictions", - CH_restrictions), + GNUNET_JSON_pack_allow_null ( + GNUNET_JSON_pack_object_incref ("restrictions", + CH_restrictions)), GNUNET_JSON_pack_bool ("fix_address", 0 == address_attempts_left), GNUNET_JSON_pack_string ("nonce",