aescfb_decrypt(9)
π aescfb_decrypt π
okay so bestie, welcome to the aescfb_decrypt(9) page from the Kernel API Manual β yes it's real, yes it's in the kernel, and yes it's lowkey iconic β¨
πΈ NAME πΈ
aescfb_decrypt β perform AES-CFB decryption on a block of data π«Ά
like, that's the whole vibe: ciphertext goes in, plaintext comes out, the math girlies handle the rest π₯
β¨ SYNOPSIS β¨
void aescfb_decrypt (const struct aes_enckey *key , u8 *dst , const u8 *src , int len , const u8 iv[AES_BLOCK_SIZE] );
no cap, that's the exact signature β copy it character for character or the compiler WILL come for you π
π ARGUMENTS π
keyβ the AES-CFB key schedule π like the whole setup of round keys, already prepared, don't come at it with a raw password, it's not that kind of function.dstβ pointer to the plaintext output buffer π¦ this is where the decrypted goodies land.srcβ pointer to the ciphertext π and here's the slay: it may equaldstfor decryption in place. same pointer, both jobs, main character energy fr fr.lenβ the size in bytes of the plaintext and ciphertext π yes both, they're the same length, that's just how CFB works bestie.ivβ the initialization vector (IV) to use for this block of data π typed asconst u8 iv[AES_BLOCK_SIZE], so it's a wholeAES_BLOCK_SIZE-sized array, mwah π
π SEE ALSO π
- the kernel file
./lib/crypto/aescfb.cβ go read the source, it's giving transparency π aescfb_encrypt(9)β the encrypt twin, the other half of the duo, check it out too πΈ
bestie reminder:srcanddstbeing allowed to be the same pointer is literally stated in the args, so in-place decryption is the vibe β but don't go inventing other behaviours, that's all the page says π
and that's the page!! π§ from ./lib/crypto, dated October 2026 β periodt, stay decrypted, ily πβ
π¦ 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