crypto_skcipher_import(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… crypto_skcipher_import(9) β€” the Kernel API Manual, bestie edition ✨

okay so you found the crypto_skcipher_import(9) page in the Kernel API Manual and you're like "what does importing even mean here" β€” don't worry, it's actually so simple. Sit down, grab a matcha πŸ“, let's go.


🌸 NAME 🌸

crypto_skcipher_import β€” literally just importing partial state 🫢

✨ SYNOPSIS ✨

int crypto_skcipher_import (struct skcipher_request *req , const void
*in );

that's it, that's the whole vibe check πŸ’€ two args, one int back.

πŸŽ€ ARGUMENTS πŸŽ€

  • req β€” the reference to the skcipher_request handle that holds, like, all the information needed to perform the operation. it's the main character of this function ngl πŸ‘‘
  • in β€” the buffer holding the state. the goods. the whole situation πŸ“¦

πŸ¦‹ DESCRIPTION πŸ¦‹

so what this does: it imports the partial state of the transformation. fr fr.

It loads the entire state of the ongoing transformation from a provided block of data, so the transformation can just... continue from this point onward. like picking a save file back up mid-game, iconic behavior tbh ✨

and listen β€” no data processing happens at this point. none. zero. it's purely a state-loading moment, so don't expect any encrypting or decrypting to sneak in here πŸ™ˆ

🌈 RETURN 🌈

  • 0 β€” if the cipher operation was successful πŸ’– slay
  • < 0 β€” if an error occurred 😭 not slay

πŸ’œ SEE ALSO πŸ’œ

the whole friend group, no cap. here's everyone, and they're all in the kernel file ./include/crypto/skcipher.h:


and that's the whole page bestie, you ate that πŸ«ΆπŸ’…

β€” signed off from ./include/crypto, dated October 2026, on the crypto_skcipher_import(9) manual page. go be iconic with your state importing πŸ§šβ€β™€οΈβ­

πŸ“¦ where this page comes from