crypto_lskcipher_decrypt(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… crypto_lskcipher_decrypt(9) β€” Kernel API Manual, bestie edition πŸŽ€

okay so this is a page from the Kernel API Manual, and the star of the show is crypto_lskcipher_decrypt β€” the little function that could, and does, decrypt stuff. she's giving "quiet main character energy" fr fr. let's get into it πŸ¦‹


✨ NAME ✨

crypto_lskcipher_decrypt β€” decrypt ciphertext. that's it. that's the whole vibe. 🫢


🌸 SYNOPSIS 🌸

int crypto_lskcipher_decrypt (struct crypto_lskcipher *tfm , const u8
*src , u8 *dst , unsigned len , u8 *siv );

look at her. iconic signature, no notes. πŸ’…


🧚 ARGUMENTS 🧚

  • tfm β€” the lskcipher handle. your girl, your cipher, your whole personality. it's the thing you're holding when you call this.
  • src β€” source buffer. the ciphertext lives here. this is the "before" pic. πŸ“Έ
  • dst β€” destination buffer. where the decrypted goodness goes. the "after" pic, slay.
  • len β€” number of bytes to process. literally just how many bytes we're cooking with. πŸ”₯
  • siv β€” IV + state for the cipher operation. bestie, read this part twice: the length of the IV must comply with the IV size defined by crypto_lskcipher_ivsize. and then, right after the IV, the IV is followed with a buffer with the length as specified by crypto_lskcipher_statesize. so it's IV then state, back to back, no gaps, no drama. πŸ™ˆ

πŸ‘‘ DESCRIPTION πŸ‘‘

Decrypt ciphertext data using the lskcipher handle. that's the whole job description. she takes your ciphertext, she uses the lskcipher handle you handed her, and she gives you back plaintext. no cap. ⭐


πŸ’€ RETURN πŸ’€

  • >=0 if the cipher operation was successful β€” and if it's positive, then this many bytes have been left unprocessed. so like, positive = it worked but there's leftovers, noted. πŸ“
  • < 0 if an error occurred. we don't love that, but we respect the transparency.
fr fr check the return value. positive means unprocessed bytes are still sitting there, and negative means something went sideways β€” don't just assume it ate. πŸ’–

🌈 SEE ALSO 🌈

Kernel file ./include/crypto/skcipher.h, plus the whole extended friend group:


okay that's the page!! source is ./include/crypto, dated October 2026, and it's all about crypto_lskcipher_decrypt(9). go forth and decrypt responsibly, bestie πŸ’œβœ¨πŸŽ€

πŸ“¦ where this page comes from