commit cef00012044bf02dc5e165f1e53f8a03b48c58c6
parent 3731a08d825f061d7f6d260f9df0d69494b0ccd7
Author: Christian Grothoff <christian@grothoff.org>
Date: Tue, 14 Jul 2026 11:22:07 +0200
new option
Diffstat:
1 file changed, 3 insertions(+), 0 deletions(-)
diff --git a/manpages/challenger.conf.5.rst b/manpages/challenger.conf.5.rst
@@ -69,6 +69,9 @@ TOKEN_EXPIRATION
How long is the access token valid after it was issued.
Optional, defaults to 1 hour if not given.
+PIN_RETRANSMISSION_FREQUENCY
+ Minimum time that must pass before the same challenge code (PIN/TAN) is (re)transmitted to the same address again. Users may ask the challenger to re-send the challenge, but such requests are ignored if the last transmission happened more recently than this. Should be (much) smaller than ``VALIDATION_DURATION``. Optional, defaults to 5 minutes if not given.
+
AUTH_COMMAND
Which command should we execute to transmit the challenge code to the address. The address is given as the first argument, while the message to send is provided on stdin. Templates (possibly without the necessary credentials) for such commands are provided as challenger-send-email.sh, challenger-send-post.sh and challenger-send-sms.sh.
