shisa_keys_find(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

💖 shisa_keys_find — the manual page, but make it make sense 💖

okay bestie, so this is shisa_keys_find(3) — a lil function from the shishi library, and honestly? she's giving key-hunting main character energy. 🎀 If you've ever needed to go digging through a principal's keys and pull out only the ones that match your vibe, this is literally the function for you. no cap.

✨ NAME ✨

shisa_keys_find — it's an API function, periodt. 💅

🌸 SYNOPSIS 🌸

#include <shisa.h>

int shisa_keys_find(Shisa * dbh, const char * realm, const char *
principal, const Shisa_key * hint, Shisa_key *** keys, size_t * nkeys);

yes bestie, that's a lot of asterisks. don't panic. 🫶

🦋 ARGUMENTS 🦋

  • Shisa * dbh — your Shisa library handle, the one you got from calling shisa(). she's the whole vibe, you need her. ✨
  • const char * realm — the name of the realm the principal belongs to. like, which kingdom are we in, yk? 👑
  • const char * principal — the name of the principal whose keys we're examining. this is who we're snooping on (lovingly). 🙈
  • const Shisa_key * hint — pointer to a Shisa_key structure stuffed with hints about what matching criteria the relevant keys should have. and if you pass NULL? she matches all keys. all of them. every single one. 💀
  • Shisa_key *** keys — this is where she hands you back a pointer to a newly allocated array of Shisa_key structures. fresh out the oven. 🔥
  • size_t * nkeys — pointer to an integer that gets updated with the number of allocated Shisa_key structures sitting in *keys. so you know how many you got. 💖

🧚 DESCRIPTION 🧚

okay so here's the tea. ☕

She iterates through the whole set of keys belonging to PRINCIPAL@REALM — selected by principal and realm — and then she extracts any keys that match the criteria in hint. it's giving "shopping for exactly the keys I want" energy. 🛍️

and the best part? not all elements of hint need to be filled in. set only the fields you're interested in, bestie, that's it. for example — and this is iconic — if you want to extract all keys of etype 3, i.e., DES-CBC-MD5, then you set the field key->etype to 3, and all other fields to zero. boom. done. slay. 💅✨

🌈 RETURN VALUE 🌈

Returns SHISA_OK if successful, or an error code. that's it. that's the whole thing. either she ate or she didn't. 😭

💀 REPORTING BUGS 💀

found a bug? don't be shy, report it 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/

ngl, they wanna 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.

(translation: share her, remix her, 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. 📖

lowkey reminder bestie: that Shisa_key *** keys is a newly allocated array, so don't just walk away from it. she's yours now. 🙈

okay that's the whole page, mwah 💋 this was shishi version 1.0.3, page shisa_keys_find(3) — go forth and find those keys, bestie. you're gonna eat. 👑🌈💜

📦 where this page comes from