fcrypt_pcbc_decrypt(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’œ fcrypt_pcbc_decrypt(9) πŸ’œ

okay so bestie, welcome to fcrypt_pcbc_decrypt(9) β€” it's a page straight out of the Kernel API Manual, and it's literally about undoing the FCrypt cipher's PCBC-mode encryption. yes, the un-fun direction. we're taking scrambled blocks and handing you back your data. slay 🫢


✨ NAME ✨

fcrypt_pcbc_decrypt β€” Decrypt data using FCrypt cipher in PCBC mode

like, that's the whole gig. decrypt. FCrypt. PCBC mode. no cap πŸ’…


🌸 SYNOPSIS 🌸

void fcrypt_pcbc_decrypt (const struct fcrypt_key *key , const u8
iv[FCRYPT_BSIZE] , const void *src , void *dst , size_t nblocks );

look at that signature, it's giving main character energy ⭐


πŸ¦‹ ARGUMENTS πŸ¦‹

  • key β€” The key πŸ”‘ like, the actual key you're decrypting with. it's a const struct fcrypt_key *, so nobody's touching it, it's just vibing there being a key.
  • iv β€” The 8-byte initialization vector πŸŽ€ fr fr, it's const u8 iv[FCRYPT_BSIZE], and FCRYPT_BSIZE is the 8-byte situation. you need it, don't lose it.
  • src β€” The source data πŸ“₯ the ciphertext lives here. const void *, so we're reading only, hands off.
  • dst β€” The destination data πŸ’Œ Both in-place and out-of-place are supported. so you can decrypt right back into the same buffer (src == dst, go off) or into a whole separate one. iconic flexibility, we love to see it.
  • nblocks β€” The number of 8-byte blocks to decrypt πŸ”’ not bytes, babes, blocks. 8-byte blocks. that distinction is gonna matter, iykyk.

🌈 SEE ALSO 🌈


lowkey a reminder: this is decrypt, so fcrypt_pcbc_encrypt(9) is your sibling page β€” if you're going the other way, that's where you wanna be πŸ™ˆ

and that's the page! 🧚 it came to us from ./net/rxrpc, dated October 2026, under the Kernel API Manual banner β€” stay encrypted out there, bestie πŸ’–πŸ“

πŸ“¦ where this page comes from