shishi_ap_req_process_keyusage(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_ap_req_process_keyusage — the shishi manual, section 3 💖

okay bestie, sit down, hydrate, because we're about to talk about shishi_ap_req_process_keyusage(3) — yes that's the whole name, it's giving "my function name is a whole sentence" and honestly? iconic. this is a page from the shishi manual (section 3, the library-call girlies), and it's an API function. let's get into it ✨

🌸 NAME 🌸

shishi_ap_req_process_keyusage — it's an API function, no cap. that's literally the whole name section and we respect the minimalism 💅

✨ SYNOPSIS ✨

the way you summon this function is:

#include <shishi.h>

int shishi_ap_req_process_keyusage(Shishi_ap * ap, Shishi_key * key,
       int32_t keyusage);

so like, include the header first (#include <shishi.h> — mandatory, she's not optional) and then you get an int back. noted. 🫶

🎀 ARGUMENTS 🎀

three args, three vibes, let's go one by one:

  • Shishi_ap * ap — the structure that holds all the info about the AP exchange. she's the container, the keeper of the lore, the main character of this whole operation. 💖
  • Shishi_key * key — the cryptographic key used to decrypt the ticket in the AP-REQ. this is your little magical girl transformation key, bestie. 🔑
  • int32_t keyusage — the key usage to use during decryption. and listen, this one has rules:
    • for normal AP-REQ's, this is normally SHISHI_KEYUSAGE_APREQ_AUTHENTICATOR
    • for AP-REQ's that are part of TGS-REQ's, this is normally SHISHI_KEYUSAGE_TGSREQ_APREQ_AUTHENTICATOR

pick the right one or it's not gonna slay, iykyk. 🙈

🦋 DESCRIPTION 🦋

okay so here's the tea. this function does a whole two-step:

  1. decrypts the ticket in the AP-REQ using the supplied key 🗝️
  2. decrypts the Authenticator in the AP-REQ using the key inside the decrypted ticket 🔓

and then — and this is the part where we celebrate — on success it sets the Ticket and Authenticator fields in the AP exchange. so it's not just decrypting for funsies, it's updating the state. periodt. 👑

⭐ RETURN VALUE ⭐

returns SHISHI_OK iff successful. that "iff" is doing a lot of heavy lifting there and we love her for it. anything else? not SHISHI_OK, bestie, read the room. 😭

💀 REPORTING BUGS 💀

found a bug? don't suffer in silence, that's not the vibe. report bugs to <bug-shishi@gnu.org>. 📧

they want to hear from you, fr fr. 🫶

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, take it, share it, remix it, 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, this command:

info shishi

should give you access to the complete manual. the way that's your one-stop shop for the whole lore. go read it, bestie. 📚

and that's the page!! 🌸 it's shishi version 1.0.3, from the shishi_ap_req_process_keyusage(3) manual page, and you're now officially caught up. go forth and decrypt responsibly. mwah 💅💖✨

📦 where this page comes from