shishi_kdcreq_...ansited_check_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_kdcreq_disable_transited_check_p — bestie's guide to the shishi manual 💖

okay so. hi. you're looking at a page from the shishi manual, section 3, and the star of the show is shishi_kdcreq_disable_transited_check_p. it's an API function, she's little, she's mighty, she answers exactly one question and she answers it correctly. periodt. ✨

🌸 NAME 🌸

shishi_kdcreq_disable_transited_check_p — API function. that's it, that's her whole job description, and honestly? iconic. 👑

🦋 SYNOPSIS 🦋

#include <shishi.h>

int shishi_kdcreq_disable_transited_check_p(Shishi * handle, Shishi_asn1
kdcreq);

like, that's the whole vibe. two args, one int coming back at you. no cap. 🎀

💅 ARGUMENTS 💅

  • Shishi * handle — the shishi handle, bestie. and where do you get one? as allocated by shishi_init(). that's the plug. don't come to the function empty-handed, she needs her handle. 🫶
  • Shishi_asn1 kdcreq — a KDC-REQ variable, and specifically the one we're pulling the kdc-options field out of. that's where the flag lives. that's the whole point. 👀

✨ DESCRIPTION ✨

so what is she doing, exactly? she determines whether the KDC-Option disable-transited-check flag is set. one flag, one answer. lowkey elegant. 💜

here's the lore, and ngl it actually matters:

by default, the KDC will check the transited field of a ticket-granting-ticket against the policy of the local realm before it will issue derivative tickets based on the ticket-granting ticket. that's the default behavior, that's the vibe check, that's the whole point of the check. 🔍

if this flag is set in the request, checking of the transited field is disabled. straight up off. and here's the consequence, and it's a real one: tickets issued without the performance of this check will be noted by the reset (0) value of the TRANSITED-POLICY-CHECKED flag, which is basically the ticket telling the application server "hey bestie, nobody checked this for you — the tranisted field must be checked locally." 🙈

and KDCs? they are encouraged but not required to honor the DISABLE-TRANSITED-CHECK option. so like… it's a suggestion. a strong suggestion. a suggestion with a cute little flag attached. do with that what you will. 💀

also important: this flag is new since RFC 1510. so if you're reading something ancient, she's not there yet. 🌈

⭐ RETURN VALUE ⭐

returns non-0 iff the disable-transited-check flag is set in KDC-REQ. so: truthy means set, zero means not set. read it and weep (with joy, probably). 🔥

😭 REPORTING BUGS 😭

found a bug? tell the shishi girlies directly, they want to know, fr fr:

Copyright © 2002-2022 Simon Josefsson.

and the license, verbatim, because we respect the paperwork in this house: 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. 🫶

🧚 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, this command:

info shishi

should give you access to the complete manual. go forth and read, bestie. 📚

and that's the whole page!! mwah 💖

sign-off time: this was shishi version 1.0.3, page shishi_kdcreq_...ansited_check_p(3). slay, stay hydrated, and always check your transited fields. 💅✨🌸

📦 where this page comes from