SASL_SETPASS(3)
π SASL_SETPASS π
okay bestie, pull up a chair, because we're talking about sasl_setpass β a page from the Cyrus SASL manual (section 3, for all my library-function girlies π«Ά).
β¨ NAME β¨
sasl_setpass β Cyrus SASL documentation. yeah, that's literally the whole name entry, she's a woman of few words but many powers π
πΈ SYNOPSIS πΈ
#include <sasl/sasl.h>
int sasl_setpass(sasl_conn_t *conn,
const char *user,
const char *pass, unsigned passlen,
const char *oldpass, unsigned oldpasslen,
unsigned flags)
π¦ DESCRIPTION π¦
int sasl_setpass(sasl_conn_t *conn,
const char *user,
const char *pass, unsigned passlen,
const char *oldpass, unsigned oldpasslen,
unsigned flags)
so like, sasl_setpass will set passwords in the sasldb, and trigger the setpass callbacks for all available mechanisms. she's the main character of password-setting, no cap. π
π Parameters π
connβ is the SASL connection context. your whole vibe container, basically.userβ is the username to set the password for. who are we doing this for, bestie?passβ the password to set.passlenβ length of the password to set (pass). yes, she needs the length too, she's thorough.oldpassβ optional. The old password.oldpasslenβ optional. The old password length.flagsβ are flags includingSASL_SET_CREATEandSASL_SET_DISABLE(to cause the creating of nonexistent accounts and the disabling of an account, respectively). so like,SASL_SET_CREATE= "make her exist β¨" andSASL_SET_DISABLE= "actually nvm, shut her down π".
ngl this next bit matters:oldpassandoldpasslenare unused in the Cyrus SASL implementation, though are passed on to any mechanisms that may require them. so in Cyrus SASL they're just chilling, but they still get handed off to whoever needs them. iykyk. π
β 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, handle them.
π SEE ALSO π
RFC 4422:saslman:sasl(3)sasl_errors(3)sasl_checkpass(3)
π AUTHOR π
The Cyrus Team. iconic. slay.
π COPYRIGHT π
1993-2016, The Cyrus Team
and that's the whole page, bestie!! this was Cyrus SASL 2.1.28, dated February 18, 2022 β mwah, love that for us. go set some passwords, you absolute legend πβ¨
π¦ 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