KCAPI_KPP_INIT(3)

✨ KCAPI_KPP_INIT ✨

okay bestie, welcome to kcapi_kpp_init(3) from the Programming Interface corner of the libkcapi manual 💖 this is the one that spins up a KPP cipher handle for you, no cap.

---

🌸 NAME 🌸

kcapi_kpp_init — initialize cipher handle 💅

---

🎀 SYNOPSIS 🎀

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

---

🦋 ARGUMENTS 🦋

• handle — [out] the cipher handle, all filled in for you by the time this call is done. it's giving "here's your new bestie" 🫶
• ciphername — [in] the kernel crypto API cipher name, exactly as it's spelled in /proc/crypto (yes, literally that file, go look 👀)
• flags — [in] flags that say what type of cipher handle you want ✨

---

💖 DESCRIPTION 💖

so this function does the whole init thing: it sets up a KPP cipher handle and opens up the connection to the kernel. main character energy, truly 👑

on success, a pointer to a kcapi_handle object gets handed back to you in *handle. and bestie, listen — you have to call kcapi_kpp_destroy afterwards to free those resources. don't leave it hanging, that's not the vibe 🙈

returns 0 upon success; -ENOENT — algorithm not available; -EOPNOTSUPP — AF_ALG family not available; -EINVAL — accept syscall failed; -ENOMEM — cipher handle cannot be allocated 💀

lowkey important: that -ENOMEM one means the cipher handle could not be allocated, so like... nothing to clean up, but also nothing to use 😭

---

⭐ AUTHOR ⭐

Stephan Mueller <smueller@chronox.de> — Author. iconic behavior, we stan 🧚

---

👑 COPYRIGHT 👑

that's the whole page, periodt 💜

---

and that's a wrap on the KCAPI_KPP_INIT(3) page, bestie — brought to you by libkcapi Manual 1.5.0, dated July 2025. go forth and initialize responsibly 🌈💖