KCAPI_AKCIPHER_INIT(3)

✨ KCAPI_AKCIPHER_INIT(3) ✨

okay bestie, we're in the libkcapi corner of the man pages, and this one is literally just about ✨manifesting✨ an asymmetric cipher handle. it's giving "step one of a whole ritual" energy and honestly? iconic. 💅

---

🌸 NAME 🌸

kcapi_akcipher_init — initialize cipher handle 🎀

---

🦋 SYNOPSIS 🦋

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

---

💖 ARGUMENTS 💖

• handle — [out] the cipher handle, which gets filled in during the call. you hand over a pointer-to-pointer and it comes back with a whole personality 🫶
• ciphername — [in] the kernel crypto API cipher name, exactly as it's specified in /proc/crypto. so like, go look at what's in there first, don't just freestyle it 😭
• flags — [in] flags that specify the type of cipher handle you want. it's the vibe check for what kind of handle you're getting ✨

---

💜 DESCRIPTION 💜

so this function does the initialization of an asymmetric cipher handle and sets up the connection to the kernel. no cap, that's the whole job — it's the "hi bestie, we're linked now" moment. 🔥

on success, a pointer to a kcapi_handle object is returned in *handle. and listen — once you've got that handle, you should call kcapi_akcipher_destroy afterwards to free the resources. it's the responsible thing, the main character thing, the cleanup after yourself thing. don't leave it hanging 💀

it returns:

• 0 upon success — slay ✨
• -ENOENT — the algorithm is not available 🙈
• -EOPNOTSUPP — the AF_ALG family is not available 💀
• -EINVAL — the accept syscall failed 😭
• -ENOMEM — the cipher handle cannot be allocated 🌧️

---

👑 AUTHOR 👑

Stephan Mueller <smueller@chronox.de> Author. 🫡

---

🎀 COPYRIGHT 🎀

that's the whole page, bestie — go forth and initialize responsibly 💖✨

libkcapi Manual 1.5.0 · July 2025 — mwah, periodt. 💅🌸🦋