shishi_keys_from_keytab_mem(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_mem — the manual page, but make it cute 💖

okay bestie, so this is a page from the shishi manual, and it's about shishi_keys_from_keytab_mem(3). it's an API function. yes, we're in the C library section, put your big-girl glasses on, we're doing this 💅

✨ NAME ✨

shishi_keys_from_keytab_mem — it's an API function, periodt.

✨ SYNOPSIS ✨

#include <shishi.h>

int shishi_keys_from_keytab_mem(Shishi * handle, const char * data,
       size_t len, Shishi_keys ** outkeys);

like, that's the whole vibe. include the header, call the thing, get keys. slay.

✨ ARGUMENTS ✨

  • Shishi * handle — the shishi handle, bestie. the one you got from shishi_init(). you can't just show up with no handle, that's not the energy we're bringing today 🫶
  • const char * data — a constant memory buffer holding a keytab that's len bytes big. it's just sitting there in memory, being all constant and unbothered ✨
  • size_t len — the size of that memory buffer with the keytab data. count your bytes, girl, they matter.
  • Shishi_keys ** outkeys — a pointer to the key set that will get allocated and populated. heads up though: the caller has to deallocate it on success. it's giving "you break it, you buy it" but make it memory management 😭

✨ DESCRIPTION ✨

so basically? you're creating a brand-new key set, and it's gonna be populated with keys from a MIT keytab data structure that's read out of a memory block. yes, from memory. not from a file. we're doing the memory thing today 👑

now here's the tea: the format of keytabs is proprietary. and this function supports the 0x0501 and 0x0502 formats. those are the two it rides for. if you want the full lore, go read the section The MIT Kerberos Keytab Binary File Format in the Shishi manual — it's a description of the reverse-engineered format, and honestly? iconic. reverse engineering a whole binary format? main character energy fr fr 🧚

✨ RETURNS ✨

  • it returns SHISHI_KEYTAB_ERROR if the data does not represent a valid keytab structure. like, if it's not a keytab, it's not a keytab, no cap 💀
  • and it returns SHISHI_OK on success. that's the one you want, bestie. chase that SHISHI_OK 🌈

✨ REPORTING BUGS ✨

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

ngl, bugs are just features that haven't been peer-reviewed yet. but still, report them 🙈

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.

like, you can copy it, you can modify it, no royalty required — just keep the copyright notice and this notice. that's the whole deal, and it's a generous deal honestly 💜

✨ 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. so if you're ever lost, girl, just run that and the whole manual opens up like a portal ✨

and that's the page, bestie 🎀 this was pulled from shishi version 1.0.3, for shishi_keys_from_keytab_mem(3). go forth, parse those keytabs, and deallocate your keyset on success, i'm literally begging you 😭🫶

📦 where this page comes from