From 23740ac41b441c3972701eb8e52541ad7c6591aa Mon Sep 17 00:00:00 2001 From: Dante Catalfamo Date: Tue, 22 Dec 2020 01:55:28 -0500 Subject: bsd-auth: Begin work on auth_challenge --- content/posts/WIP-how-bsd-authentication-works/index.org | 13 +++++++++++++ 1 file changed, 13 insertions(+) (limited to 'content') diff --git a/content/posts/WIP-how-bsd-authentication-works/index.org b/content/posts/WIP-how-bsd-authentication-works/index.org index b741f17..de2b651 100644 --- a/content/posts/WIP-how-bsd-authentication-works/index.org +++ b/content/posts/WIP-how-bsd-authentication-works/index.org @@ -909,6 +909,19 @@ :CUSTOM_ID: auth_challenge :END: + #+begin_src c + char *auth_challenge(auth_session_t *as) + #+end_src + + =auth_challenge=, much like [[#auth_verify][=auth_verify=]] is a function that acts as + a front-end for [[#auth_call][=auth_call=]], except used specifically for + challenges. + + First the session =as= is checked. If it's =NULL=, or =as->style= is + =NULL=, =as->name= is =NULL=, or if the username begins with a + hyphen, or has a length of zero, the function returns =NULL=. + + <> * auth_userresponse :PROPERTIES: -- cgit v1.2.3