crypto_lskcipher_chunksize(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 crypto_lskcipher_chunksize(9) β€” Kernel API Manual 🌸

okay bestie, welcome to the manual page for crypto_lskcipher_chunksize(9), straight out of the Linux Kernel API Manual πŸ’… this one's short but it's important, so pay attention.


✨ NAME ✨

crypto_lskcipher_chunksize β€” obtain chunk size πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

unsigned int crypto_lskcipher_chunksize (struct crypto_lskcipher *tfm );

πŸ’– ARGUMENTS πŸ’–

  • tfm β€” the cipher handle. that's it, that's the whole vibe. it's your little handle to the cipher you're working with 🫢

πŸ’… DESCRIPTION πŸ’…

okay so here's the tea β˜• β€” for ciphers like CTR, the block size is set to one. one! literally just one. wild, i know.

but β€” and this is the part people miss β€” you still need to provide incremental updates in multiples of the underlying block size, because the IV does not have sub-block granularity. the IV is not out here doing fractional little baby steps, she's a whole-block girlie πŸ’€

this concept, this "how much do you actually have to feed me at a time" number, is known in this API as the chunk size. main character energy, honestly πŸ‘‘ and now you know, iykyk.


⭐ RETURN ⭐

the chunk size, in bytes. that's it. that's the return value πŸ”₯


🌈 SEE ALSO 🌈

buckle up bestie, this list is long β€” but every single one of these is your friend πŸ’œ


ngl, that's a lot of cross-references, but slay, you got this 🧚

and that's the whole page, bestie πŸ’– this lil gem lives under ./include/crypto, dated October 2026, and it's filed as crypto_lskcipher_chunksize(9) β€” periodt. go forth and chunk responsibly πŸ“

πŸ“¦ where this page comes from