shishi_ap_etype_tktoptionsdata(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_etype_tktoptionsdata — the shishi manual, bestie edition ✨

okay so this is a page from the shishi manual (section 3, the library-call girlies 💅), and it's all about shishi_ap_etype_tktoptionsdata. yes that's a mouthful, yes we're gonna get through it together, no cap. 🫶

🌸 NAME 🌸

shishi_ap_etype_tktoptionsdata — it's an API function, bestie. that's the whole vibe. ✨

🎀 SYNOPSIS 🎀

#include <shishi.h>

int shishi_ap_etype_tktoptionsdata(Shishi * handle, Shishi_ap ** ap,
int32_t etype, Shishi_tkt * tkt, int options, const char * data, size_t
len);

like. look at all those parameters. she's doing the MOST and honestly? we respect it. 👑

🦋 ARGUMENTS 🦋

  • Shishi * handle — the shishi handle, allocated by shishi_init(). literally the main character of every shishi function ever. 🫶
  • Shishi_ap ** ap — a pointer to the new structure that holds all the info about the AP exchange. it's giving "here's where the receipts live". 💖
  • int32_t etype — the encryption type of the newly generated random subkey. spicy cryptography moment. 🔥
  • Shishi_tkt * tkt — the ticket that gets set in the newly created AP. she's the guest of honor. 🎀
  • int options — the AP-REQ options to set in the newly created AP. little switches, big consequences. ✨
  • const char * data — the input array with the data to checksum in the Authenticator. yes, checksum. no, i will not elaborate further, it's literally in the name. 🌸
  • size_t len — the length of that input array with the data to checksum in the Authenticator. because data without len is just chaos. 💀

🌈 DESCRIPTION 🌈

okay so here's the tea ☕ — this function creates a brand new AP exchange using shishi_ap(), and then it sets the ticket, the AP-REQ apoptions, and the Authenticator checksum data using shishi_ap_set_tktoptionsdata().

then, because she's extra in the best way, a random session key gets added to the authenticator — using the same keytype as the ticket. iconic behavior, honestly. matching sets, but for cryptography. 💅

⭐ RETURN VALUE ⭐

returns SHISHI_OK iff successful. that's it. that's the whole mood. if you got SHISHI_OK you ATE. 🔥

🙈 REPORTING BUGS 🙈

found a bug? don't be shy, tell the devs! report bugs to <bug-shishi@gnu.org>. 📧

they literally want to hear from you, bestie. it's not a trap. 🫶

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. licensing that just lets you live your life. 🌈

💜 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, it's giving scholarly. 📚✨

and that's the page, bestie!! this little writeup is from shishi version 1.0.3, and the man page itself is shishi_ap_etype_tktoptionsdata(3) — section 3, library calls only, we stay in our lane. 💖 mwah, go checksum something. 🎀✨

📦 where this page comes from