SASL_SERVER_START(3)
π sasl_server_start(3) β Cyrus SASL π
okay bestie, welcome to the Cyrus SASL corner of the man pages, you're gonna do great, i promise π«Ά
β¨ NAME β¨
sasl_server_start β Cyrus SASL documentation π
πΈ SYNOPSIS πΈ
#include <sasl/sasl.h>
int sasl_server_start(sasl_conn_t * conn,
const char * mech,
const char * clientin,
unsigned clientinlen,
const char ** serverout,
unsigned * serveroutlen);
π¦ DESCRIPTION π¦
so here's the vibe, the signature laid out all long and pretty:
int sasl_server_start(sasl_conn_t * conn,
const char * mech,
const char * clientin,
unsigned * clientinlen,
const char ** serverout,
unsigned * serveroutlen);
sasl_server_start() begins the authentication with the mechanism specified with mech. This fails if the mechanism is not supported. like, no support, no entry, sorry babe π
π Parameters
connβ is the SASL connection contextmechβ is the mechanism name that the client requestedclientinβ is the client initial response,NULLif the protocol lacks support for clientβsendβfirst or if the other end did not have an initial send. Note that no initial client send is distinct from an initial send of a null string, and the protocol MUST account for this difference. π yes this distinction is real and yes it matters, do not conflate them, fr frclientinlenβ is the length of initial responseserveroutβ is created by the plugin library. It is the initial server response to send to the client. This is allocated/freed by the library and it is the job of the client to send it over the network to the server. Also protocol specific encoding (such as base64 encoding) must needs to be done by the server.serveroutlenβ is set to the length of initial server challenge
π RETURN VALUE π
SASL callback functions should return SASL return codes. See sasl.h for a complete list. SASL_OK is returned if the authentication is complete and the user is authenticated. SASL_CONTINUE is returned if one or more steps are still required in the authentication. π₯
All other return values indicate errors and should be handled or the authentication session should be quit. π¨
bestie. if it's notSASL_OKand notSASL_CONTINUE, it's giving error, and you either handle it or you end the session. no third option, periodt.
π SEE ALSO π
RFC 4422,:saslman:sasl(3), sasl_server_init(3), sasl_server_new(3), sasl_server_step(3), sasl_errors(3)
π AUTHOR π
The Cyrus Team
π COPYRIGHT π
1993-2016, The Cyrus Team
and that's the whole page, you ate it π
β¨ version 2.1.28, dated February 18, 2022, courtesy of the Cyrus SASL girlies β mwah, go write some slay authentication code ππ¦π
π¦ 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