shisa_key_update(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_key_update — the glow-up page for your keys ✨

okay bestie, so this is a page from the shishi manual, section 3, and it's literally about shisa_key_update 🎀 — the function that gives an existing key in the database a little makeover. no cap.

🌸 SYNOPSIS 🌸

#include <shisa.h>

int shisa_key_update(Shisa * dbh, const char * realm, const char *
principal, const Shisa_key * oldkey, const Shisa_key * newkey);

that's it. that's the whole vibe. 🦋

✨ ARGUMENTS ✨

  • Shisa * dbh — the Shisa library handle, and you gotta make it with shisa() first. no handle, no entry, periodt.
  • const char * realm — the name of the realm your principal lives in. 🏰
  • const char * principal — the name of the principal that needs its key updated. main character of this operation fr.
  • const Shisa_key * oldkey — a pointer to a Shisa_key structure that gives the matching criteria for finding the key you wanna update. it's like the search filter, not the full story. 🔍
  • const Shisa_key * newkey — a pointer to a complete Shisa_key structure, where all the fields get used for the new key. 💖 note that oldkey normally has wayyy fewer fields filled in — like, embarrassingly fewer. 🙈

🫶 DESCRIPTION 🫶

so what it does: it modifies data about a key stored in the database — a key that belongs to the principal you picked with principal and realm.

here's the two-step. first, oldkey is used to locate the key to update, exactly like shisa_keys_find() does it. then, the key it found gets modified to carry whatever info is stored in newkey. glow-up complete. 💅

the way that not all elements of oldkey need to be filled out — you only need sufficiently many of them to uniquely identify the key you're after. ✨ for example: if you wanna modify the info stored about a unique key of etype 3, i.e. DES-CBC-MD5, then set the field key->etype to 3, leaving all other fields as zero. iconic, minimal, effective. 🎀

⭐ RETURN VALUE ⭐

  • SHISA_OK — slay, it worked. ✅
  • SHISA_NO_KEY — couldn't locate any key. 😭
  • SHISA_MULTIPLE_KEY_MATCH — more than a single key matched your criteria, bestie. you gotta be more specific.
  • or, an error code otherwise. 💀

😭 REPORTING BUGS 😭

found a bug? 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/

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. fr fr, 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. iykyk 📖✨

and that's the whole page, bestie — this was shishi version 1.0.3, shisa_key_update(3). go update those keys, you absolute icon. 💜🦋

📦 where this page comes from