challenger

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

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

bump protocol version to v8

Diffstat:
Msrc/challenger/challenger-httpd_config.c | 3++-
1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/challenger/challenger-httpd_config.c b/src/challenger/challenger-httpd_config.c @@ -34,6 +34,7 @@ * 5: added support for GET /authorize to have a link in challenge messages to the form * 6: added ``address_type`` field in ``/config`` * 7: added ``build_version`` field in ``/config`` + * 8: minor HTTP status code corrections */ @@ -62,7 +63,7 @@ CH_handler_config (struct CH_HandlerContext *hc, GNUNET_JSON_pack_object_incref ("restrictions", CH_restrictions), GNUNET_JSON_pack_string ("version", - "7:0:5")); + "8:0:6")); } return MHD_queue_response (hc->connection, MHD_HTTP_OK,