KCAPI_AEAD_INBUFLEN_(3)

πŸ’… KCAPI_AEAD_INBUFLEN_(3) β€” the "how much room does my decryption buffer need" girlie

okay bestie, welcome to section 3 of the libkcapi Manual (Programming Interface division, we're fancy like that ✨). This one is a lil function with a big name: kcapi_aead_inbuflen_dec. Say it three times fast, I dare you. πŸŽ€


🌸 NAME 🌸

kcapi_aead_inbuflen_dec β€” returns the minimum decryption input buffer length, no cap, fr fr


✨ SYNOPSIS ✨

size_t kcapi_aead_inbuflen_dec(struct kcapi_handle * handle,
                               size_t inlen, size_t assoclen,
                               size_t taglen);

like... four arguments and a size_t return, she's lowkey minimalist πŸ’…


🫢 ARGUMENTS 🫢

  • handle β€” [in] the cipher handle, aka the main character of this whole operation πŸ‘‘
  • inlen β€” [in] the size of the ciphertext, literally how many bytes of scrambled data you're holding
  • assoclen β€” [in] the size of the associated data, aka AD (yes, that's the abbrev, iykyk)
  • taglen β€” [in] the size of the authentication tag, the lil proof-of-vibes that everything is legit πŸ”₯

🌈 DESCRIPTION 🌈

bestie, she returns the minimum size of output data length in bytes. That's it. That's the whole job. She tells you how much space you gotta have so you don't under-allocate and end up in buffer-overflow city 😭


πŸ’– AUTHOR πŸ’–

Stephan Mueller <smueller@chronox.de> β€” the author, the icon, the moment. 🌟


(standard copyright section, she's keeping it mysterious πŸ™ˆ)


no cap, always trust the return value before you malloc, queen. your future self will thank you. πŸ’œ

and that's the whole page, bestie!! πŸŽ€ this was the libkcapi Manual 1.5.0, dated July 2025, section KCAPI_AEAD_INBUFLEN_(3) β€” slay, ate, left no crumbs, periodt. βœ¨πŸ’…πŸŒˆ

πŸ“¦ where this page comes from