aescfb_decrypt(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… 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 equal dst for 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 as const u8 iv[AES_BLOCK_SIZE], so it's a whole AES_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: src and dst being 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