SASL_CHECKAPOP(3)
β¨ SASL_CHECKAPOP(3) β¨
okay bestie, welcome to the Cyrus SASL manual, section 3 (that's the library-functions girlies π
). today's main character is sasl_checkapop, and she is so much simpler than she looks. let's get into it π«Ά
πΈ NAME πΈ
sasl_checkapop β Cyrus SASL documentation, but make it a vibe check on your APOP challenge/response π
π¦ SYNOPSIS π¦
#include <sasl/sasl.h>
int sasl_checkapop(sasl_conn_t *conn,
const char *challenge,
unsigned challen,
const char *response,
unsigned resplen)
π DESCRIPTION π
int sasl_checkapop(sasl_conn_t *conn,
const char *challenge,
unsigned challen,
const char *response,
unsigned resplen)
so like. sasl_checkapop will check an APOP challenge/response. that's the whole job, she's focused, she's employed π
APOP is an optional POP3 (RFC 1939) authentication command which uses a shared secret (aka a password, bestie, it's just a password π). and where does that password live? in the SASL secrets database. iconic storage, no notes.
wanna know more about the SASL shared secrets database? that's a System Administrators Guide situation, go read that one π
also super important: if you call this with a NULL challenge, sasl_checkapop() will check to see if the APOP mechanism is enabled. that's it. just a little "are you even on, queen?" moment β
π RETURN VALUE π
sasl_checkapop returns an integer which corresponds to one of the following codes.
SASL_OKβ the authentication is complete. slay. π
All other return codes indicate errors and should either be handled or the authentication session should be quit. like, do not ignore them, bestie, that's not the move π
see sasl_errors(3) for meanings of return codes. iykyk π
π§ CONFORMING TO π§
RFC 4422, RFC 1939 β she's certified, she's compliant, she's that girl β¨
π SEE ALSO π
π AUTHOR π
The Cyrus Team π«Ά
π COPYRIGHT π
1993-2016, The Cyrus Team
and that's the whole page, bestie!! this was Cyrus SASL version 2.1.28, dated February 18, 2022 β no cap, that's the real source and date, mwah π go forth and authenticate responsibly πΈππ
π¦ where this page comes from
- alpine 3.22: cyrus-sasl-doc 2.1.28-r8 Β· BSD-3-Clause-Attribution AND BSD-4-Clause
- alpine 3.23: cyrus-sasl-doc 2.1.28-r9 Β· BSD-3-Clause-Attribution AND BSD-4-Clause
- alpine 3.24: cyrus-sasl-doc 2.1.28-r9 Β· BSD-3-Clause-Attribution AND BSD-4-Clause
- centos-stream 10: cyrus-sasl-devel 2.1.28-27.el10 Β· BSD-Attribution-HPND-disclaimer
- fedora 43: cyrus-sasl-devel 2.1.28-33.fc43 Β· BSD-Attribution-HPND-disclaimer
- fedora 43: cyrus-sasl-devel 2.1.28-33.fc43 Β· BSD-Attribution-HPND-disclaimer
- fedora 44: cyrus-sasl-devel 2.1.28-35.fc44 Β· BSD-Attribution-HPND-disclaimer
- fedora 44: cyrus-sasl-devel 2.1.28-35.fc44 Β· BSD-Attribution-HPND-disclaimer
- opensuse-leap 16.0: cyrus-sasl-bdb-devel 2.1.28-160000.4.1 Β· BSD-4-Clause
- opensuse-leap 16.0: cyrus-sasl-bdb-devel 2.1.28-160000.4.1 Β· BSD-4-Clause
- opensuse-leap 16.0: cyrus-sasl-bdb-devel 2.1.28-160000.4.1 Β· BSD-4-Clause
- opensuse-leap 16.0: cyrus-sasl-bdb-devel 2.1.28-160000.4.1 Β· BSD-4-Clause
- opensuse-leap 16.0: cyrus-sasl-devel 2.1.28-160000.4.1 Β· BSD-4-Clause
- opensuse-leap 16.0: cyrus-sasl-devel 2.1.28-160000.4.1 Β· BSD-4-Clause
- opensuse-leap 16.0: cyrus-sasl-devel 2.1.28-160000.4.1 Β· BSD-4-Clause
- opensuse-leap 16.0: cyrus-sasl-devel 2.1.28-160000.4.1 Β· BSD-4-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms