SYMMETRIC KEY CIPHER REQUEST HANDLE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… Symmetric Key Cipher Request Handle πŸ’…

okay so this one's from the Kernel API Manual, and it's genuinely such a sleeper hit β€” like everyone's out here obsessing over the big crypto calls and nobody's giving the request handle its flowers. but bestie, without this little icon the whole symmetric key cipher op literally cannot happen. so let's get into it 🫢


✨ NAME ✨

skcipher_request β€” the handle that holds every pointer you need for a symmetric key cipher operation πŸ”‘


πŸŽ€ DESCRIPTION πŸŽ€

So the skcipher_request data structure is like the main character's bag β€” it contains all the pointers to data required for the symmetric key cipher operation. every single one. no cap. πŸ’…

What's in the bag, you ask? bestie, let me tell you:

  • the cipher handle β€” and here's the cute part, the cipher handle can be used by multiple skcipher_request instances, she's popular πŸ‘‘
  • a pointer to plaintext and a pointer to ciphertext
  • the asynchronous callback function
  • etc. β€” yes the original literally says etc., and yes I'm keeping it, because that's what it says 🌸
ngl the way this works is genuinely elegant: skcipher_request acts as a handle to the skcipher_request_* API calls in a similar way as the skcipher handle does to the crypto_skcipher_* API calls. like, sibling energy. matched set. it's giving symmetry (pun intended, I'm not sorry) πŸ’€βœ¨

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./include/crypto/skcipher.h, plus the whole friend group right here β€” every single one of these:

like I said. the whole group chat. πŸ’–


okay that's the page!! before I go β€” this one lives in ./include/crypto and it's dated October 2026, and it's filed under the lovely abbreviated title Symmetric K...quest Handle(9) in case you're searching for it. mwah, go read the rest of the crypto API, you're gonna slay πŸŒˆπŸ’œ

πŸ“¦ where this page comes from