KCAPI_AEAD_INIT(3)

💖 kcapi_aead_init(3) — the libkcapi glow-up 💖

okay bestie, sit DOWN, because we're about to talk about kcapi_aead_init from the libkcapi manual, and honestly? it's giving ✨ establishing a connection to the kernel ✨ and I'm obsessed.

---

🌸 NAME 🌸

kcapi_aead_init — literally just the initialization of a cipher handle, no biggie, just your girl getting the whole thing set up 🎀

---

✨ SYNOPSIS ✨

int kcapi_aead_init(struct kcapi_handle ** handle,
                    const char * ciphername, uint32_t flags);

---

🦋 ARGUMENTS 🦋

• handle — [out] the cipher handle, which gets filled in during the call 🫶
• ciphername — [in] the kernel crypto API cipher name, exactly as specified in /proc/crypto (yes, that file, go look 👀)
• flags — [in] the flags that specify the type of cipher handle 💅

---

💜 DESCRIPTION 💜

so here's the vibe: this function initializes an AEAD cipher handle and establishes the connection to the kernel. main character energy, fr fr 👑

On success, a pointer to the kcapi_handle object is returned in *handle. And bestie, listen — you gotta call kcapi_aead_destroy afterwards to free the resources. Don't leave it hanging, that's not cute 😭

and now the returns, no cap:

• 0 upon success 🎉
• -ENOENT — algorithm not available 💀
• -EOPNOTSUPP — AF_ALG family not available 🙈
• -EINVAL — accept syscall failed
• -ENOMEM — cipher handle cannot be allocated 😭

like, not me listing every single one of these error codes with my whole chest, but you NEED them, iykyk 🧚

---

🌈 AUTHOR 🌈

Stephan Mueller <smueller@chronox.de>

• Author. that's it, that's the credit, and we stan 👑

---

🍓 COPYRIGHT 🍓

---

and that's the whole page, bestie!! 💖 this was libkcapi Manual version 1.5.0, dated July 2025 — mwah, slay, periodt ✨🎀💅