SASL_VERIFYFILE_T(3)

✨ NAME ✨

sasl_verifyfile_t — Cyrus SASL documentation, bestie 💖

---

🌸 SYNOPSIS 🌸

#include <sasl/sasl.h>

typedef enum {
    SASL_VRFY_PLUGIN, /* a DLL/shared library plugin */
    SASL_VRFY_CONF,   /* a configuration file */
    SASL_VRFY_PASSWD, /* a password storage file */
    SASL_VRFY_OTHER   /* some other file type */
} sasl_verify_type_t

int sasl_verifyfile_t(void *context,
                const char *file,
                sasl_verify_type_t type)

---

🦋 DESCRIPTION 🦋

okay so, presenting the function signature, no notes:

int sasl_verifyfile_t(void *context,

const char *file,

sasl_verify_type_t type)

sasl_verifyfile_t() is literally the vibe-check function for files 👑 — it checks whether a given file is okay for use by the SASL library. The whole point is letting applications sanity check the environment, fr fr. Like, say you want to make sure that plugins or the config file cannot be written to? Yeah. That's the moment. main character energy for file security 💅

💜 Parameters

• context – context from the callback record
• context – context from the callback record
• file – full path of the file to verify
• type – type of the file.

not me noticing that context is listed twice up there 💀 that's exactly how it is in the original, so we're keeping both, no cap. Two context bullets, zero context added. iconic behaviour honestly.

---

🌈 RETURN VALUE 🌈

SASL callback functions should return SASL return codes. See sasl.h for a complete list. SASL_OK indicates success. ✨

Other return codes indicate errors and should be handled. do NOT ignore those, bestie, handle them, periodt 🙈

---

🎀 SEE ALSO 🎀

• RFC 4422
• :saslman:sasl(3)
• sasl_callbacks(3)
• sasl_errors(3)

---

👑 AUTHOR 👑

The Cyrus Team 🫶

---

💖 COPYRIGHT 💖

1993-2016, The Cyrus Team

---

okay that's the whole page, you ate it, go forth and verify some files 🧚⭐ this was Cyrus SASL version 2.1.28, dated February 18, 2022 — and yes the manual is literally titled SASL_VERIFYFILE_T(3), iykyk 🌸💜