summaryrefslogtreecommitdiffstats
path: root/content/posts/WIP-how-bsd-authentication-works
diff options
context:
space:
mode:
Diffstat (limited to 'content/posts/WIP-how-bsd-authentication-works')
-rw-r--r--content/posts/WIP-how-bsd-authentication-works/index.org13
1 files changed, 13 insertions, 0 deletions
diff --git a/content/posts/WIP-how-bsd-authentication-works/index.org b/content/posts/WIP-how-bsd-authentication-works/index.org
index 9c49297..fc9aaf0 100644
--- a/content/posts/WIP-how-bsd-authentication-works/index.org
+++ b/content/posts/WIP-how-bsd-authentication-works/index.org
@@ -853,11 +853,24 @@
:CUSTOM_ID: auth_userchallenge
:END:
+ #+begin_src c
+ auth_session_t *auth_userchallenge(char *name, char *style, char *type, char **challengep)
+ #+end_src
+
+ =auth_userchallenge= is used when the authentication style requires
+ that the user be presented with a challenge, but the user cannot be
+ directly interacted with over the terminal. As an example, this
+ might be used in cases where the user is using S/KEY authentication
+ over SSH.
* auth_userresponse
:PROPERTIES:
:CUSTOM_ID: auth_userresponse
:END:
+ #+begin_src c
+ int auth_userresponse(auth_session_t *as, char *response, int more)
+ #+end_src
+
* COMMENT note :noexport: