SASL_GETOPT_T(3)
π SASL_GETOPT_T(3) π
okay bestie, welcome to the Cyrus SASL corner of the manual, section 3, and today's main character is sasl_getopt_t. yes it's a whole page just for one callback. she's iconic like that. π
β¨ NAME β¨
sasl_getopt_t β Cyrus SASL documentation. that's it, that's the name, she's literally just documentation-core and we respect it. π
πΈ SYNOPSIS πΈ
#include <sasl/sasl.h>
int sasl_getopt_t(void *context,
const char *plugin_name,
const char *option,
const char ** result,
unsigned * len);
look at her. five parameters. no cap, she's doing the most and we love her for it. π¦
π DESCRIPTION π
int sasl_getopt_t(void *context,
const char *plugin_name,
const char *option,
const char ** result,
unsigned * len);
so here's the tea β β sasl_getopt_t is used to retrieve an option from the application, and it's often mechanism specific. like, a real example? asking which KERBEROS_V4 srvtab file to use. yeah. she's out here fetching your config vibes. β¨
π§ Parameters π§
contextβ is the SASL connection context. your connection's whole identity, basically her main character energy.plugin_nameβ is the plugin this value is for. you gotta know who you're shopping for.optionβ is a string representing the option. and bestie, listen: a common option that all server applications should handle is the method for checking plaintext passwords. see the administrators guide for a full description of this option. iykyk. π
π«Ά Memory management π«Ά
Memory management of options supplied by the getopt callback should be done by the application. that part's on you, bestie, no take-backs.
however β and this is the important part β any requested option must remain available until the callback is no longer valid. that means:
- when
sasl_dispose(3)is called for the connection it is associated with, or - when
sasl_done(3)is called for global callbacks.
don't be out here freeing stuff early, that's giving chaos and we are NOT about that life. π
π₯ RETURN VALUE π₯
SASL callback functions should return SASL return codes. see sasl.h for a complete list. SASL_OK indicates success. π
Other return codes indicate errors and should be handled. fr fr, don't ignore them, they're trying to tell you something.
π SEE ALSO π
RFC 4422,:saslman:sasl(3)sasl_errors(3)sasl_callbacks(3)
go read them, they're all part of the same friend group. π
π AUTHOR π
The Cyrus Team. legends, honestly.
π COPYRIGHT π
1993-2016, The Cyrus Team
and that's the whole page, bestie!! you ate that. slay. periodt. π β¨
this was version 2.1.28, dated February 18, 2022 β mwah, love that for us. π¦πΈπ
π¦ 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