shishi_as_process(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_as_process(3) β€” the shishi manual, bestie edition πŸ’«

okay so this is a page from the shishi manual, and it's about shishi_as_process β€” an API function, no cap. pull up a chair, we're doing Kerberos things πŸŽ€


✨ NAME ✨

shishi_as_process β€” it's an API function, bestie. that's the whole name. iconic.


🌸 SYNOPSIS 🌸

#include <shishi.h>

int shishi_as_process(Shishi * handle, Shishi_asn1 asreq, Shishi_asn1
asrep, const char * string, Shishi_asn1 * enckdcreppart);

like. look at that signature. it's giving main character energy 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • Shishi * handle β€” your Shishi handle, the one you got from shishi_init(). this is the emotional support handle. you need it.
  • Shishi_asn1 asreq β€” input variable, holding the transmitted KDC-REQ. the request that got sent out into the world πŸ•ŠοΈ
  • Shishi_asn1 asrep β€” input variable, holding the received KDC-REP. the reply that came back. the vibe check result.
  • const char * string β€” input variable with a null terminated password. yes bestie, a password, in a const char *, null terminated, exactly like that. guard it with your life πŸ”
  • Shishi_asn1 * enckdcreppart β€” output variable returning a new EncKDCRepPart. it's a pointer-to, so it hands you a whole new thing. obsessed.

πŸ’– DESCRIPTION πŸ’–

so what does this actually DO. it processes an AS client exchange and returns the decrypted EncKDCRepPart, which is the thing holding all the details about the received ticket. the lore. the tea. β˜•

and the way it does it is so lowkey elegant: this function simply derives the encryption key from the password, and then calls shishi_kdc_process(). that's it. that's the whole plot. derive key β†’ hand off to shishi_kdc_process(). periodt. πŸ’…


πŸ”₯ RETURN VALUE πŸ”₯

returns SHISHI_OK if the AS client exchange was successful πŸŽ‰

but bestie. be so for real. multiple failure conditions are possible. it's not always gonna be SHISHI_OK. check your returns. i'm literally begging you πŸ™


😭 REPORTING BUGS 😭

found a bug? first of all, relatable. second of all, report it 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.

(so basically: go off, just keep the receipts πŸ’œ)


🌈 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. iykyk ✨


friendly reminder bestie: everything above is exactly as the original says it β€” no invented behaviour, no made-up flags, no extra tips dressed up as facts. the vibes are new. the facts are untouched. 🧚

sign-off time πŸŽ€ this was shishi_as_process(3), from the shishi manual, version 1.0.3. stay encrypted, stay iconic, and may all your exchanges return SHISHI_OK πŸ’–βœ¨πŸ¦‹