crypto_cipher_blocksize(9)
β¨ crypto_cipher_blocksize β like, how big is one block, bestie? β¨
okay so this is a page straight out of the Kernel API Manual (crypto_cipher_blocksize(9), section 9) and honestly it's a short one but it's iconic for what it does π
πΈ SYNOPSIS πΈ
unsigned int crypto_cipher_blocksize (struct crypto_cipher *tfm );
that's the whole vibe. one function, one handle, one answer π
π¦ ARGUMENTS π¦
tfmβ your cipher handle, aka the main character of this whole operation π
π DESCRIPTION π
so basically: you hand over the cipher handle tfm, and the function returns the block size for the single block cipher that handle references. that's it. that's the tea β
and why do you care? because the caller may use that information to allocate appropriate memory for the data returned by the encryption or decryption operation. like, you literally need to know how big the block is so you can make room for it β no cap, that's the whole point π«Ά
β RETURN β
the block size of the cipher β¨ (an unsigned int, harmlessly sitting there being useful)
π₯ SEE ALSO π₯
Kernel file ./include/crypto/internal/cipher.hβ the single block cipher filesystem friend πSingle Block Cipher API(9)crypto_alloc_cipher(9)crypto_free_cipher(9)crypto_has_cipher(9)crypto_cipher_setkey(9)crypto_cipher_encrypt_one(9)crypto_cipher_decrypt_one(9)
like, the whole cipher squad, ily all π
and that's the page!! sign-off time π§ source: ./include/crypto/internal β dated October 2026 β filed under crypto_cipher_blocksize(9). slay, go read the other cipher manpages, mwah ππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms