shishi_tgs_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_tgs_process ✨

okay bestie, welcome to shishi_tgs_process β€” it's from the shishi manual, section 3, and it's literally the glow-up step for your TGS client exchange πŸ’…


🌸 NAME 🌸

shishi_tgs_process β€” it's an API function, no cap πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

#include <shishi.h>

int shishi_tgs_process(Shishi * handle, Shishi_asn1 tgsreq, Shishi_asn1
tgsrep, Shishi_asn1 authenticator, Shishi_asn1 oldenckdcreppart,
Shishi_asn1 * enckdcreppart);

πŸŽ€ ARGUMENTS πŸŽ€

  • Shishi * handle β€” the Shishi handle, and you gotta get it from shishi_init() first, periodt. That's the whole vibe.
  • Shishi_asn1 tgsreq β€” an input variable holding the transmitted KDC-REQ. The one you sent out into the world πŸ•ŠοΈ
  • Shishi_asn1 tgsrep β€” an input variable holding the received KDC-REP. The one that came back πŸ’Œ
  • Shishi_asn1 authenticator β€” an input variable with an authenticator that got extracted from the AP-REQ part of tgsreq. Sneaky little guy, iykyk πŸ”₯
  • Shishi_asn1 oldenckdcreppart β€” an input variable with the EncKDCRepPart that was used in the request. The before pic πŸ“Έ
  • Shishi_asn1 * enckdcreppart β€” an output variable holding the new EncKDCRepPart. The after pic ✨ main character energy fr fr

πŸ’œ DESCRIPTION πŸ’œ

So here's the tea β˜• β€” this function processes a TGS client exchange and outputs the decrypted EncKDCRepPart, which is holding all the deets about the received ticket.

The way it works is lowkey elegant: it simply derives the encryption key from the ticket that was used to construct the original TGS request, and then it calls shishi_kdc_process(). That's it. That's the whole arc. Iconic 🫢


🌈 RETURN VALUE 🌈

Returns SHISHI_OK if the TGS client exchange was successful β€” slay πŸŽ‰

Failures include ASN.1 and TGS conditions. So like, if it doesn't go off, that's where it went wrong 😭


πŸ™ˆ REPORTING BUGS πŸ™ˆ

Found a bug? Not the vibe. Report bugs 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. Fr fr, that's the license, respect it πŸ’–


⭐ 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 it bestie, it's giving encyclopedia πŸ“šβœ¨


🫢 that's the whole page, you ate it

k bye, this was shishi version 1.0.3, page shishi_tgs_process(3) β€” mwah πŸ’‹πŸŒΈπŸ§š