shishi_tkt_may_postdate_p(3)
π shishi_tkt_may_postdate_p(3) π
okay bestie, welcome to the shishi manual, section 3 β and today's main character is shishi_tkt_may_postdate_p, an API function that checks one very specific little flag for you. no cap. let's get into it β¨
β¨ NAME β¨
shishi_tkt_may_postdate_p β it's an API function, bestie. that's the whole vibe.
πΈ SYNOPSIS πΈ
#include <shishi.h>
int shishi_tkt_may_postdate_p(Shishi_tkt * tkt);
π ARGUMENTS π
Shishi_tkt * tktβ your input variable, holding the ticket info. that's it. she's the only one here. π
π¦ DESCRIPTION π¦
so what does she actually do? she determines if the ticket may be used to grant postdated tickets. periodt.
now here's the lore, because this flag is lowkey misunderstood:
the MAY-POSTDATE flag in a ticket is normally only interpreted by the ticket-granting service. it can be ignored by application servers β like, they just don't care, it's not their business, they're giving main character energy elsewhere. π
this flag MUST be set in a ticket-granting ticket in order to issue a postdated ticket based on the presented ticket. it is reset by default. it MAY be requested by a client by setting the ALLOW-POSTDATE option in the KRB_AS_REQ message. (yes, that's ALLOW- and POSTDATE with a line break in the original, but it's one option name, iykyk.)
this flag does not allow a client to obtain a postdated ticket-granting ticket. postdated ticket-granting tickets can only be obtained by requesting the postdating in the KRB_AS_REQ message. so likeβ¦ don't try it, bestie, that's not what this is for. π
the life (endtime-starttime) of a postdated ticket will be the remaining life of the ticket-granting ticket at the time of the request β unless the RENEWABLE option is also set, in which case it can be the full life (endtime-starttime) of the ticket-granting ticket. and the KDC MAY limit how far in the future a ticket may be postdated. so there are limits, and the KDC is the one holding the clipboard. π
π₯ RETURN VALUE π₯
returns non-0 iff the may-postdate flag is set in the ticket. so: truthy = yes she may, falsy = nope. π«Ά
π REPORTING BUGS π
found a bug? not you being the chosen one. π report bugs to <bug-shishi@gnu.org>.
- GNU Shishi home page:
http://www.gnu.org/software/shishi/ - General help using GNU software:
http://www.gnu.org/gethelp/
π COPYRIGHT π
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. slay, honestly. that's so generous of him. π
π 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 her, she's thorough. π
and that's the whole page, bestie!! π this was shishi_tkt_may_postdate_p(3) from the shishi manual, version 1.0.3. thanks for reading all the way down, you're literally the best. mwah πβ¨
π¦ where this page comes from
- debian bookworm: shishi-doc 1.0.3-1 Β· GPL-3.0-or-later
- debian trixie: shishi-doc 1.0.3-5 Β· GPL-3.0-or-later
- nixos 26.05: shishi 1.0.3
- nixpkgs unstable: shishi 1.0.3
- ubuntu noble: shishi-doc 1.0.3-2.1build2 Β· GPL-3.0-or-later
- ubuntu questing: shishi-doc 1.0.3-5
- ubuntu resolute: shishi-doc 1.0.3-5build1 Β· GPL-3.0-or-later
- ubuntu stonking: shishi-doc 1.0.3-7 Β· GPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms