crypto_skcipher_encrypt(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… crypto_skcipher_encrypt β€” bestie, we're ENCRYPTING

okay so this is a page straight out of the Kernel API Manual (yes, kernel docs can be cute, we contain multitudes) and it's about crypto_skcipher_encrypt. it does exactly what it says on the tin: encrypts plaintext. that's it. that's the whole vibe. ✨


🌸 SYNOPSIS 🌸

int crypto_skcipher_encrypt (struct skcipher_request *req );

literally one function, one pointer, one int coming back at you. we love a minimal icon. πŸŽ€


πŸ¦‹ ARGUMENTS πŸ¦‹

  • req β€” a reference to the skcipher_request handle that holds all the info needed to actually perform the cipher operation. it's giving "everything you need is in the bag already" energy. πŸ‘œ

πŸ’– DESCRIPTION πŸ’–

so here's the tea: this function encrypts plaintext data using that skcipher_request handle. πŸ”₯

and if you're sitting there like "ok but how do i even fill that thing with data??" β€” no worries bestie, that whole situation is discussed with the skcipher_request_* functions. go read those, they're the main characters of that particular storyline. πŸ“–βœ¨


πŸ‘‘ RETURN πŸ‘‘

  • 0 β€” slay, the cipher operation was successful πŸ’…
  • < 0 β€” nope, an error occurred 😭 (negative number = the vibe check failed)

🌈 SEE ALSO 🌈

okay this list is long but we're getting through it together, iykyk:


friendly reminder bestie: the _skcipher and _lskcipher families are two different friend groups and you should not mix them up just because they hang out in the same header file. πŸ’€

and that's the whole page!! 🫢 this lil gem lives in ./include/crypto, dated October 2026, and it's part of the Kernel API Manual β€” go forth and encrypt responsibly, mwah πŸ’œπŸ§šβ€β™€οΈ

πŸ“¦ where this page comes from