shishi_tkt_proxiable_p(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_tkt_proxiable_p(3) β€” the shishi manual's own little vibe check πŸ’…

okay bestie, sit down, hydrate, because we're doing a ✨function✨ today. This one lives in the shishi manual, and it's short, sweet, and honestly iconic. Let's go. 🫢


🌸 NAME 🌸

shishi_tkt_proxiable_p β€” API function. That's it. That's the name. She's an API function and she's thriving. πŸ‘‘


✨ SYNOPSIS ✨

#include <shishi.h>

int shishi_tkt_proxiable_p(Shishi_tkt * tkt);

Like. Two lines. A whole header include and one function call. No cap. 🌈


πŸŽ€ ARGUMENTS πŸŽ€

  • Shishi_tkt * tkt β€” bestie, this is your input variable with ticket info. That's the one job. You hand her a ticket, she tells you things about it. It's giving "tell me everything, don't be shy." πŸ’–

πŸ¦‹ DESCRIPTION πŸ¦‹

So the actual mission here? Determine if ticket is proxiable. Simple. Elegant. Fr fr.

Now let's talk about what proxiable even means, because the lore is kinda everything. 🧚

The PROXIABLE flag in a ticket is normally only interpreted by the ticket-granting service. It can be ignored by application servers. (Not me learning that app servers just don't care πŸ’€)

When set, this flag tells the ticket-granting server that it is OK to issue a new ticket β€” but not a ticket-granting ticket β€” with a different network address based on this ticket. Read that again. New ticket: yes. Ticket-granting ticket: absolutely not. The audacity would be unreal. πŸ™ˆ

This flag is set if requested by the client on initial authentication. And by default, the client will request that it be set when requesting a ticket-granting ticket, and reset when requesting any other ticket. So like, the default behaviour is already doing the most correct thing. Periodt. πŸ’…


⭐ RETURN VALUE ⭐

Returns non-0 iff proxiable flag is set in ticket.

That's the whole answer. Non-zero = flag's set. Zero = she's not proxiable. Binary queen behaviour. πŸ‘‘


😭 REPORTING BUGS 😭

Found a bug? Don't suffer in silence, bestie, that's not the vibe. Report bugs to <bug-shishi@gnu.org>.

They literally want to hear from you. Communication is key. 🫢


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 like β€” go off, remix it, share it, just keep the receipts. Respect the origin, y'know? πŸŽ€


πŸ”₯ 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. It's giving "the full lore is in the group chat archive." Go read it. πŸ“š


lowkey the entire page is like 12 lines of actual facts and yet it ate. no notes. πŸ’–

and that's the whole thing, bestie β€” this one's from shishi 1.0.3, page shishi_tkt_proxiable_p(3). go forth and check your flags. mwah. πŸ’…βœ¨