SASL_GETPROP(3)
π SASL_GETPROP(3) π
okay bestie, gather round, we're reading a Cyrus SASL manpage and honestly? it's giving informative. this one lives in the Cyrus SASL manual, section 3, and it's all about peeking at the little properties attached to your SASL connection. no cap. π¦
β¨ NAME β¨
sasl_getprop β Cyrus SASL documentation
like, that's literally it. the name is the name. periodt. π
πΈ SYNOPSIS πΈ
#include <sasl/sasl.h>
int sasl_getprop(sasl_conn_t *conn,
int propnum,
const void ** pvalue);
π DESCRIPTION π
so, the signature one more time, because we love a full look:
int sasl_getprop(sasl_conn_t *conn,
int propnum,
const void ** pvalue);
sasl_getprop gets the value of a SASL property. that's the whole vibe. π«Ά
why would you even want that? okay so picture this: after a successful authentication, a server might lowkey wanna know the authorization name. or maybe a client app is curious about the strength of the negotiated security layer. both totally valid. both iconic. β¨
π Parameters
connβ is the SASL connection contextpropnumβ is the identifier for the property requestedpvalueβ is filled on success. List of properties:
π The Property List (the main character moment)
SASL_USERNAMEβ pointer to NUL terminated user nameSASL_SSFβ security layer security strength factor, if 0, call tosasl_encode(3),sasl_decode(3)unnecessarySASL_MAXOUTBUFβ security layer max output buf unsignedSASL_DEFUSERREALMβ server authentication realm usedSASL_GETOPTCTXβ context for getopt callbackSASL_IPLOCALPORTβ local address stringSASL_IPREMOTEPORTβ remote address stringSASL_SERVICEβ service passed tosasl_*_newSASL_SERVERFQDNβ serverFQDN passed tosasl_*_newSASL_AUTHSOURCEβ name of auth source last used, useful for failed authentication trackingSASL_MECHNAMEβ active mechanism name, if anySASL_PLUGERRβ similar tosasl_errdetail
π 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. don't just ignore them bestie, that's not the move. π
π§ SEE ALSO π§
RFC 4422,:saslman:sasl(3), sasl_errors(3) sasl_server_new(3), sasl_client_new(3)
π AUTHOR π
The Cyrus Team π
π COPYRIGHT π
1993-2016, The Cyrus Team
and that's the whole page, bestie! no skips, no crumbs, every single property accounted for. ate and left no crumbs fr fr. π β¨
version 2.1.28 π dated February 18, 2022 π
mwah, love u, go read sasl.h if you want the full return code lore π«Άπ
π¦ 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