SASL_ERRSTRING(3)

πŸ’– SASL_ERRSTRING(3) πŸ’–

okay bestie, gather round, it's Cyrus SASL time and we're looking at sasl_errstring β€” the lil glow-up machine that turns your sad little integer error code into actual words a human can read πŸ¦‹


✨ NAME ✨

sasl_errstring β€” Cyrus SASL documentation πŸ’…


✨ SYNOPSIS ✨

#include <sasl/sasl.h>

const char * sasl_errstring(int saslerr,
    const char * langlist,
    const char ** outlang);

✨ DESCRIPTION ✨

so here's the whole vibe, fr fr:

const char * sasl_errstring(int saslerr,

const char * langlist,

const char ** outlang);

sasl_errstring gets called when you wanna convert a SASL return code (yes, the integer one, the cryptic one, the one that's giving absolutely nothing) into a human readable string. ✨ At this time the only language available is American English. no cap. that's it. that's the whole menu. πŸ™ˆ

heads up bestie: if that string is gonna get sent to the client, a server should call sasl_usererr(3) on a return code first. do not skip this step, it's important πŸ‘‘

🌸 Parameters 🌸

  • saslerr β€” this is the error number you wanna convert. the mystery number. the little guy. πŸ”’
  • langlist β€” currently unused. Use NULL. that's literally it, she does nothing, she's just here for the plot 🫢
  • outlang β€” specifies the desired RFC 1766 language for output. NULL defaults to "en-us"; currently the only supported language. so like… NULL it is, bestie πŸŽ€

πŸ’€ real talk moment: this function is not the recommended means of extracting error code information from SASL. instead, your application should use sasl_errdetail(3), which contains this information (and more). like, she's the main character, this one is the understudy. iykyk 😭

✨ RETURN VALUE ✨

Returns the string. πŸŽ‰ And if langlist is NULL, US-ASCII is used.


✨ SEE ALSO ✨


✨ AUTHOR ✨

The Cyrus Team πŸ‘‘


1993-2016, The Cyrus Team


and that's the tea πŸ“ this lil page is from Cyrus SASL 2.1.28, dated February 18, 2022 β€” mwah, love that for us, periodt πŸ’…βœ¨