crypto_skcipher_chunksize(9)

✨ NAME ✨

okay bestie, you're looking at the manual page for crypto_skcipher_chunksize(9) 💖 and the name-vibe is literally: crypto_skcipher_chunksize - obtain chunk size. that's the whole mission, periodt. 🎀

🦋 SYNOPSIS 🦋

unsigned int crypto_skcipher_chunksize (struct crypto_skcipher *tfm );

🌸 ARGUMENTS 🌸

• tfm — cipher handle. yes ma'am, that's the handle you're passing in 🫶

💅 DESCRIPTION 💅

so here's the tea, bestie: for ciphers such as CTR, the block size is set to one. but you still need to provide incremental updates in multiples of the underlying block size, because the IV does not have sub-block granularity. in this API, that whole situation is known as the chunk size. no cap, that's the detail. 🌈

⭐ RETURN ⭐

chunk size in bytes. iconic. 💅

👑 SEE ALSO 👑

like, go read these too, iykyk:

• Kernel file ./include/crypto/skcipher.h
• struct skcipher_request(9)
• struct skcipher_alg(9)
• struct lskcipher_alg(9)
• Symmetric Key Cipher API(9)
• crypto_alloc_skcipher(9)
• crypto_alloc_lskcipher(9)
• crypto_free_skcipher(9)
• crypto_free_lskcipher(9)
• crypto_has_skcipher(9)
• crypto_skcipher_ivsize(9)
• crypto_lskcipher_ivsize(9)
• crypto_skcipher_blocksize(9)
• crypto_lskcipher_blocksize(9)
• crypto_lskcipher_chunksize(9)
• crypto_skcipher_statesize(9)
• crypto_lskcipher_statesize(9)
• crypto_skcipher_setkey(9)
• crypto_lskcipher_setkey(9)
• crypto_skcipher_reqtfm(9)
• crypto_skcipher_encrypt(9)
• crypto_skcipher_decrypt(9)
• crypto_skcipher_export(9)
• crypto_skcipher_import(9)
• crypto_lskcipher_encrypt(9)
• crypto_lskcipher_decrypt(9)
• Symmetric Key Cipher Request Handle(9)
• crypto_skcipher_reqsize(9)
• skcipher_request_set_tfm(9)
• skcipher_request_alloc(9)
• skcipher_request_free(9)
• skcipher_request_set_callback(9)
• skcipher_request_set_crypt(9)

k bye, this page is brought to you by ./include/crypto, dated October 2026 — it's the crypto_skcipher_chunksize(9) manual, and yes she ate 💅✨