SASL_CHALPROMPT_T(3)

πŸ’– sasl_chalprompt_t(3) β€” a Cyrus SASL moment πŸ’–

okay bestie, so this one lives in the Cyrus SASL manual, section 3 (that's the library-calls girlies), and it's literally all about asking the user for input when the server comes at you with a challenge. no cap. πŸ¦‹


✨ NAME ✨

sasl_chalprompt_t β€” Cyrus SASL documentation


🌸 SYNOPSIS 🌸

#include <sasl/prop.h>

int sasl_chalprompt_t(void *context, int id,
    const char *challenge,
    const char *prompt, const char *defresult,
    const char **result, unsigned *len)

πŸ’… DESCRIPTION πŸ’…

int sasl_chalprompt_t(void *context,

int id,

const char *challenge,

const char *prompt,

const char *defresult,

const char **result,

unsigned *len)

so sasl_chalprompt_t is the callback that prompts for input in response to a server challenge. like, the server says something, and you gotta go get the human's answer. it's giving middleman energy, but make it ✨necessary✨.

πŸŽ€ Parameters πŸŽ€

  • context – is the context from the callback record
  • id – is the callback id (either SASL_CB_ECHOPROMPT or SASL_CB_NOECHOPROMPT)
  • challenge – the server's challenge
  • prompt – A prompt for the user
  • defresult – Default result (may be NULL)
  • len – Length of the user's response.

🫢 Result 🫢

The user's response (a NUL terminated string) or SASL error code.

ngl, SASL_CB_ECHOPROMPT vs SASL_CB_NOECHOPROMPT is the whole vibe check here β€” one shows what you type, one absolutely does not. πŸ‘€

πŸ”₯ RETURN VALUE πŸ”₯

The user's response (NUL terminated), or a SASL error code. See sasl_errors(3).


🌈 SEE ALSO 🌈


πŸ‘‘ AUTHOR πŸ‘‘

The Cyrus Team


1993-2016, The Cyrus Team


and that's the whole page, bestie β€” version 2.1.28, dated February 18, 2022, brought to you by the Cyrus Team, who lowkey ate with this callback. go prompt somebody. slay. πŸ’…βœ¨