skcipher_request_set_crypt(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… skcipher_request_set_crypt(9) πŸ’…

okay so this is a page straight out of the Kernel API Manual (yes, the kernel has lore too 🌸), and it's all about skcipher_request_set_crypt β€” the function that tells your symmetric-cipher request where the data actually lives. bestie, it's giving "matchmaker for buffers" and I'm obsessed 🫢


✨ NAME ✨

skcipher_request_set_crypt β€” set data buffers πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

void skcipher_request_set_crypt (struct skcipher_request *req , struct
scatterlist *src , struct scatterlist *dst , unsigned int cryptlen ,
void *iv );

πŸŽ€ ARGUMENTS πŸŽ€

  • req β€” the request handle. your main character struct πŸ‘‘
  • src β€” source scatter / gather list. where the bytes are coming from 🌈
  • dst β€” destination scatter / gather list. where the bytes are going to 🎯
  • cryptlen β€” number of bytes to process from src. literal count, no cap πŸ”’
  • iv β€” the IV for the cipher operation, and it must comply with the IV size defined by crypto_skcipher_ivsize ⚠️ (not negotiable, she has a size and she sticks to it πŸ’…)

⭐ DESCRIPTION ⭐

So what does it actually do? This function allows setting of the source data and destination data scatter / gather lists. that's the whole gig, and she does it flawlessly ✨

Now here's the important part, so listen up 🧚:

  • For an encryption operation, the source is treated as the plaintext and the destination is the ciphertext πŸ”
  • For a decryption operation, the use is reversed β€” the source is the ciphertext and the destination is the plaintext πŸ”“

it's giving "same function, two moods" and honestly? iconic πŸ˜­πŸ’œ

ngl, if you mix up src and dst on a decrypt, that's a vibe check you will fail πŸ’€ keep the direction straight!

🌸 SEE ALSO 🌸

Kernel file ./include/crypto/skcipher.h β€” and also literally all of these besties:


and that's the tea β˜• this page lives in ./include/crypto, dated October 2026 🌈 go set those buffers, bestie, you got this fr fr πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from