KCAPI_KPP_KEYGEN_AIO(3)

📦
version 1.5.0 · 7 versions
, in fedora 43

✨ KCAPI_KPP_KEYGEN_AIO(3) ✨

okay bestie, welcome to the Programming Interface section of the libkcapi manual 💖 this one's kcapi_kpp_keygen_aio and it's literally the moment you generate a public key, asynchronous one-shot style 🦋

🎀 NAME 🎀

kcapi_kpp_keygen_aio — generate a public key (asynchronous one shot) 👑

✨ SYNOPSIS ✨

ssize_t kcapi_kpp_keygen_aio(struct kcapi_handle * handle,
                             struct iovec * outiov, size_t iovlen,
                             int access);

🌸 ARGUMENTS 🌸

  • handle — [in] the cipher handle, your main character 🫶
  • outiov — [out] head of the scatter-gather list of the destination buffers that get filled with the generated public key ✨
  • iovlen — [in] how many scatter-gather list entries there are, fr fr 🔢
  • access — [in] the kernel access type. Your options are:
    • KCAPI_ACCESS_HEURISTIC — use the internal heuristic for the fastest kernel access 👑
    • KCAPI_ACCESS_VMSPLICE — use vmsplice access 🧚
    • KCAPI_ACCESS_SENDMSG — sendmsg access 💌

💅 DESCRIPTION 💅

So here's the tea: the individual scatter-gather list entries get processed with separate invocations of the given cipher. One at a time, no cap 😭

The memory should be aligned at the page boundary using posix_memalign(sysconf(_SC_PAGESIZE)). And like, if it's not aligned at the page boundary, the vmsplice call may not send all data to the kernel. That's the vibe check you do not wanna fail ⚠️

not me warning you about alignment again — align your memory bestie, it's giving self care 💖

Return number of bytes verify upon success; a negative errno-style error code if an error occurred. Slay when it works, 😭 when it doesn't.

🌈 AUTHOR 🌈

Stephan Mueller <smueller@chronox.de>

  • Author. iconic behavior honestly 💜

and that's the whole page bestie, you ate 🍓 this was libkcapi Manual 1.5.0 from July 2025 — KCAPI_KPP_KEYGEN_AIO(3) out 💅✨

📦 where this page comes from