shishi_keys_from_keytab_file(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_keys_from_keytab_file β€” the manual page, but make it make sense πŸ’–

okay bestie, so this is the page for shishi_keys_from_keytab_file(3) β€” it lives in the shishi manual (section 3, the library-call girlies), and it's literally just an API function. sit down, grab a strawberry drink πŸ“, and let's get into it.


✨ NAME ✨

shishi_keys_from_keytab_file β€” it's an API function. that's the whole name section, she's lowkey mysterious but we love her.


🌸 SYNOPSIS 🌸

the way you pull this into your code:

#include <shishi.h>

int shishi_keys_from_keytab_file(Shishi * handle, const char * filename,
       Shishi_keys ** outkeys);

periodt. three arguments, one int coming back at you. πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • Shishi * handle β€” your shishi handle, the one you got from shishi_init(). she's the main character, everything needs her.
  • const char * filename β€” the name of the file you wanna read. yeah, just the file name. iconic.
  • Shishi_keys ** outkeys β€” a pointer to the key set that's gonna get allocated and populated for you. ⚠️ heads up bestie: the caller has to deallocate it on success. it's yours now, you take care of it, no ghosting.

πŸ¦‹ DESCRIPTION πŸ¦‹

so what does she actually do? she creates a brand new key set, and fills it up with keys pulled from a MIT keytab data structure that she read from a file. like, a whole glow-up for your empty key set. ✨

now, the keytab format? proprietary, ngl. 😭 but this function has your back β€” she supports the 0x0501 and 0x0502 formats. if you wanna know what's actually going on in there, go read the section The MIT Kerberos Keytab Binary File Format in the Shishi manual β€” it describes the whole reverse-engineered format. reverse engineering ate, fr fr. πŸ”₯


πŸ‘‘ RETURNS πŸ‘‘

she gives back an int, and here's the vibe check:

  • SHISHI_IO_ERROR β€” if the file cannot be read. 😭 tragic, the file said no.
  • SHISHI_KEYTAB_ERROR β€” if the data cannot be parsed as a valid keytab structure. it's giving "this is not a keytab, bestie."
  • SHISHI_OK β€” on success. slay! πŸ’… the good ending.

πŸ› REPORTING BUGS πŸ›

found a bug? don't suffer in silence, tell the people:

Report bugs to <bug-shishi@gnu.org>.

they literally want to hear from you, no cap. 🫢


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 basically: 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, the command

info shishi

should give you access to the complete manual. iykyk β€” go read the full thing, it's the director's cut. πŸ“–πŸ’–


and that's the page, bestie!! πŸŽ€ source is shishi, version 1.0.3, and it's the shishi_keys_from_keytab_file(3) page β€” shoutout to the whole shishi fam, ily, go populate some key sets. πŸ’…πŸ¦‹β­