fcrypt_pcbc_encrypt(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… fcrypt_pcbc_encrypt(9)

okay so this is a page from the Kernel API Manual, and bestie, we need to talk about it 🫢


✨ NAME ✨

fcrypt_pcbc_encrypt β€” encrypt your data using the FCrypt cipher in PCBC mode πŸ”₯


🌸 SYNOPSIS 🌸

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

like, that's the whole vibe. five arguments, one function, zero chill ✨


πŸŽ€ ARGUMENTS πŸŽ€

  • key β€” the key πŸ’œ that's it, that's the argument, she's the key.
  • iv β€” the 8-byte initialization vector 🌈 yes, 8 bytes, FCRYPT_BSIZE if we're being fancy.
  • src β€” the source data πŸ“ where the plaintext lives.
  • dst β€” the destination data πŸ’– both in-place and out-of-place are supported, so do whatever feels right, no cap.
  • nblocks β€” the number of 8-byte blocks to encrypt πŸ”’ count 'em. carefully. 8-byte blocks, bestie, not bytes.

πŸ’€ DESCRIPTION πŸ’€

WARNING: This cipher is insecure. 🚨 Not only is the 56-bit key easily brute-forced, the cipher itself is cryptographically weak and doesn't even provide the intended 56-bit security level. It effectively just acts as an obfuscation algorithm. It is supported only for backwards compatibility.

okay so first thing you need to know: this is not it. like not me recommending this cipher ever πŸ™ˆ

the 56-bit key? easily brute-forced. the cipher itself? cryptographically weak, and it doesn't even actually deliver the 56-bit security level it was supposedly going for. the way that it just... doesn't. 😭

so realistically it's giving obfuscation, not encryption. it's a vibe, not a security guarantee. it exists purely for backwards compatibility β€” like that one friend who's still using an ancient phone and honestly? we support them. periodt. πŸ‘‘


πŸ¦‹ SEE ALSO πŸ¦‹

iykyk 🌟


kay that's the whole page, bestie! this one's from the ./net/rxrpc corner of the kernel, dated October 2026, and it lives in the Kernel API Manual β€” mwah, slay, stay safe out there and maybe don't encrypt anything important with it πŸ’…βœ¨

πŸ“¦ where this page comes from