gsasl_server_step(3)
π gsasl_server_step β the "one step at a time bestie" era
okay so we're in the gsasl manual, section 3, and today's main character is gsasl_server_step. it's an API function, it lives in the gsasl.h universe, and lowkey it's the server-side half of a SASL handshake. she's a little vintage, she's a little deprecated, but she ate and we respect her. π
β¨ NAME β¨
gsasl_server_step β API function π
πΈ SYNOPSIS πΈ
#include <gsasl.h>
int gsasl_server_step(Gsasl_session * sctx, const char * input, size_t
input_len, char * output, size_t * output_len);
π¦ ARGUMENTS π¦
Gsasl_session * sctxβ the libgsasl server handle. this is your girl, your session, your whole situation. keep her close π«Άconst char * inputβ input byte array. the bytes the client is sending you.size_t input_lenβ size of input byte array. how many bytes are we talking. be honest.char * outputβ output byte array. where you write your reply back at 'em.size_t * output_lenβ size of output byte array. the receipts, length edition.
π DESCRIPTION π
bestie. listen. this does one step of SASL authentication, on the server side. literally one step. not the whole dance, just one move. π
here's the tea: it reads data from the client (that's input and input_len), it processes it β and yes, it may potentially invoke callbacks to the application while doing so, so don't be shocked when your callbacks get pinged β and then it writes data back to the client, dropping it into the variables output and output_len. β¨
β οΈ no cap, important: the contents of theoutputbuffer is unspecified if this function returns anything other thanGSASL_NEEDS_MORE. unspecified!! so please don't go reading it and thinking you know what's in there. π
Return value, and this part matters: it returns GSASL_OK if authenticated terminated successfully π, GSASL_NEEDS_MORE if more data is needed π, or an error code π.
π« DEPRECATED π«
use gsasl_step() instead. that's it, that's the whole note. she's been superseded, she's passing the torch, we still love her though. π₯²
π REPORTING BUGS π
found a bug? spill. report bugs to <bug-gsasl@gnu.org> π§
- General guidelines for reporting bugs:
http://www.gnu.org/gethelp/ - GNU SASL home page:
http://www.gnu.org/software/gsasl/
π COPYRIGHT π
Copyright Β© 2002-2021 Simon Josefsson.
Copying and distribution of this file, with or without modification, are permitted in any medium without royalty provided the copyright notice and this notice are preserved. (iconic behaviour honestly, no notes π )
π₯ SEE ALSO π₯
the full documentation for gsasl is maintained as a Texinfo manual. if the info and gsasl programs are properly installed at your site, the command
info gsasl
should give you access to the complete manual. as an alternative you may obtain the manual from:
http://www.gnu.org/software/gsasl/manual/
iykyk. go read the manual, it's giving β¨knowledgeβ¨.
and that's the whole page, bestie!! this was gsasl 1.10.0, and we're signing off from gsasl_server_step(3) β stay authenticated, stay hydrated, and remember: one step at a time. π§ππ·
π¦ where this page comes from
- ubuntu jammy: libgsasl-dev 1.10.0-5 Β· GPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms