SASL_GETSECRET_T(3)

💖 NAME 💖

sasl_getsecret_t — Cyrus SASL documentation, bestie. That's the whole vibe. It's giving "the callback that hands over your secret."

---

✨ SYNOPSIS ✨

#include <sasl/sasl.h>

int sasl_getsecret_t(sasl_conn_t *conn,
                    void *context,
                    int id,
                    sasl_secret_t ** psecret);

---

🎀 DESCRIPTION 🎀

okay so here's the whole function again, laid out all dramatic:

int sasl_getsecret_t(sasl_conn_t *conn,

void *context,

int id,

sasl_secret_t ** psecret);

sasl_getsecret_t() is literally the function you use to retrieve the secret from the application. Like, the app is holding the secret, and this is the little hand-off moment. 🫶

And here's the part you cannot skip: a sasl_secret_t should be allocated to length sizeof(sasl_secret_t) + <length of secret>. Yes, you read that right — you size it for the struct plus the actual secret, not just the struct. Slay but make it correct. 💅

It's got two fields, and you need both:

• len — which is the length of the secret in bytes.
• data — which contains the secret itself (and ngl, it does not need to be null terminated).

🌸 Parameters

• conn – is the SASL connection context

fr fr, that's the parameter list. Just conn. Don't come for me, I'm only the messenger. 😭

---

🔥 RETURN VALUE 🔥

SASL callback functions should return SASL return codes. See sasl.h for a complete list — it's all in there, go look, iykyk. ✨

SASL_OK indicates success. iconic. perfect. no notes. 👑

Other return codes indicate errors and should be handled. Not optional, bestie. Handle them. 🙈

---

🦋 SEE ALSO 🦋

RFC 4422, :saslman:sasl(3), sasl_callbacks(3)

---

💜 AUTHOR 💜

The Cyrus Team

---

🌈 COPYRIGHT 🌈

1993-2016, The Cyrus Team

---

and that's the whole page, periodt. 💖✨ This one's from Cyrus SASL 2.1.28, dated February 18, 2022 — she's an older icon but she still ate. 🎀🦋 go forth and allocate your secrets correctly, mwah 💅