shishi_crypto_decrypt(3)

πŸ“¦
version 1.0.3 Β· 2 versions
  • 1.0.3 Β· debian bookworm, debian trixie, nixos 26.05, nixpkgs unstable, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking (latest)
  • 1.0.2 Β· ubuntu jammy
, in debian bookworm, debian trixie, nixos 26.05, nixpkgs unstable, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– shishi_crypto_decrypt β€” the one where we unlock the data ✨

okay so bestie, welcome to the shishi_crypto_decrypt(3) page from the shishi manual πŸŽ€ β€” this is the glow-up where your encrypted lil blob gets turned back into readable bytes. no cap.


🌸 NAME 🌸

shishi_crypto_decrypt β€” it's an API function, periodt πŸ’…


✨ SYNOPSIS ✨

#include <shishi.h>

int shishi_crypto_decrypt(Shishi_crypto * ctx, const char * in, size_t
inlen, char ** out, size_t * outlen);

she's a five-argument girlie and she's serving πŸ”₯


🫢 ARGUMENTS 🫢

  • Shishi_crypto * ctx β€” the crypto context, and literally the only place you should get one of these from is shishi_crypto(). that's the vibe, don't freelance it πŸ’œ
  • const char * in β€” your input array, aka the data you wanna decrypt. the locked-up lil thing πŸ™ˆ
  • size_t inlen β€” how big that input array is. size of the data to decrypt, that's it, that's the girl 🌸
  • char ** out β€” output array with the newly allocated decrypted data. she's fresh, she's new, somebody's gotta free her eventually (see below, iykyk) ✨
  • size_t * outlen β€” output variable that tells you how big that newly allocated output array is πŸ“

πŸ’… DESCRIPTION πŸ’…

so what she does is decrypt data, using the info hanging out in the context β€” like the key and the initialization vector. all that good stuff lives in ctx and she just... uses it. main character energy fr fr πŸ‘‘

the IV is updated inside the context after this call. like, not before, not during β€” after. so heads up that your context is not the same context it was a second ago πŸ¦‹

and then β€” the important part β€” when the application no longer needs to use the context, it should deallocate resources associated with it by calling shishi_crypto_close(). do not ghost your context, bestie, that's rude and also a leak 😭


⭐ RETURN VALUE ⭐

Returns SHISHI_OK iff successful. iff!! that's the whole bar. clear it or don't πŸ’€


πŸ› REPORTING BUGS πŸ›

found a bug? spill to <bug-shishi@gnu.org> πŸ“§


Copyright Β© 2002-2022 Simon Josefsson.

Copying and distribution of this file, with or without modification, are permitted in any medium without royalty provided the copyright notice and this notice are preserved.

(yeah she's royalty-free, go off, redistribute responsibly πŸŽ€)


🌈 SEE ALSO 🌈

The full documentation for shishi is maintained as a Texinfo manual. If the info and shishi programs are properly installed at your site, the command

info shishi

should give you access to the complete manual. go read the whole thing, it's giving βœ¨πŸ“š


and that's the page, bestie!! this was shishi_crypto_decrypt(3) from shishi 1.0.3, brought to you by the shishi gang β€” mwah, stay decrypted, stay hydrated πŸ’–πŸ¦‹πŸŒΈ