From 09b8036c0e5c05a276c6f1011d4e0e9743ef5deb Mon Sep 17 00:00:00 2001
From: Dante Catalfamo
Date: Tue, 22 Dec 2020 00:42:32 -0500
Subject: bsd-auth: Add function sig for userchallenge/response

---
 content/posts/WIP-how-bsd-authentication-works/index.org | 13 +++++++++++++
 1 file changed, 13 insertions(+)

(limited to 'content/posts/WIP-how-bsd-authentication-works')

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:
 
-- 
cgit v1.2.3