KCAPI_RNG_INIT(3)

📦
version 1.5.0 · 7 versions
, in fedora 43

✨ NAME ✨

kcapi_rng_init — bestie, this is the one that gets your cipher handle initialized, okurrr 💅

It's from the Programming Interface manual, section 3, and honestly? iconic behavior.

🌸 SYNOPSIS 🌸

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

🎀 ARGUMENTS 🎀

  • handle — [out] the cipher handle that gets filled up during the call. yes bestie, this one's the output, she's giving main character energy and she's coming back to you 🫶
  • ciphername — [in] the kernel crypto API cipher name, exactly as it's specified in /proc/crypto. not vibes-based, actual file, actual name, no cap 🦋
  • flags — [in] flags that specify the type of cipher handle. for RNG this one is literally unused, she's just here for the plot 🙈

💖 DESCRIPTION 💖

Okay so, this function initializes a random number generator handle and — the important part — establishes the connection to the kernel 🔥 That's the whole thing. That's the vibe check. RNG handle, connected, done.

On success, a pointer to a kcapi_handle object is returned in *handle. So like, you get your handle back through that pointer. 💫

After that, you should call kcapi_rng_destroy to free the resources. Not me forgetting to clean up... don't be that girl. kcapi_rng_destroy afterwards, periodt. 👑

And here's the return situation, so you know exactly what you're getting:

  • returns 0 upon success — slay ✨
  • -ENOENT — algorithm 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> — the author. king behavior fr fr 👑

And that's the whole page, bestie 🎀 just so you know where you are: this is libkcapi Manual 1.5.0, from July 2025 — KCAPI_RNG_INIT(3) — go forth and initialize responsibly, ily 🌸🦋💖

📦 where this page comes from