KDESTROY(1)

πŸ“¦
version 1.22.1 Β· 3 versions
, in ubuntu resolute, ubuntu stonking

πŸ’… KDESTROY β€” bestie edition (from the MIT Kerberos manual, kdestroy(1)) ✨


✨ NAME ✨

okay so kdestroy β€” it destroys your Kerberos tickets. that's the whole job. it's the "okay bye i'm logging off" button for your auth πŸŽ€


🌸 SYNOPSIS 🌸

kdestroy [-A] [-q] [-c cache_name] [-p princ_name]

πŸ¦‹ DESCRIPTION πŸ¦‹

so the kdestroy utility destroys the user's active Kerberos authorization tickets β€” and the way it does that is by overwriting and deleting the credentials cache that contains them. like, not just ghosting the tickets, actually scribbling over them and then yeeting the cache. iconique, honestly πŸ’…

if the credentials cache isn't specified, then the default credentials cache is the one that gets destroyed. no cache left behind, periodt.


πŸ’– OPTIONS πŸ’–

  • -A β€” destroys all caches in the collection, if a cache collection is actually available. you can pair it with -c to say exactly which collection should get destroyed. it's giving "spring cleaning but for every cache you own" 🧹✨
  • -q β€” run quietly. normally kdestroy will beep at you if it fails to destroy the user's tickets (rude of it, tbh 😭). the -q flag suppresses this behavior. so it goes full stealth mode, no noise.
  • -c cache_name β€” use cache_name as the credentials (ticket) cache name and location. if you don't use this option, the default cache name and location get used instead.

just so you know β€” the default credentials cache may vary between systems. and if the KRB5CCNAME environment variable is set, then its value is what's used to name the default ticket cache. so like, check your env before you assume anything, bestie πŸ™ˆ

  • -p princ_name β€” if a cache collection is available, destroy the cache for princ_name instead of the primary cache. can be used with the -c option to specify which collection gets searched. very "i'm not mad at the whole collection, i'm mad at this one" energy πŸ’€

πŸŽ€ NOTE πŸŽ€

most installations recommend that you place the kdestroy command in your .logout file, so that your tickets are destroyed automatically when you log out. basically: set it and forget it, and your tickets clean themselves up on the way out. self-care 🫢

🌈 ENVIRONMENT 🌈

see kerberos for a description of Kerberos environment variables. that's where the lore lives πŸ“–


⭐ FILES ⭐

  • FILE:/tmp/krb5cc_%{uid} β€” default location of Kerberos 5 credentials cache

πŸ‘‘ SEE ALSO πŸ‘‘

kinit, klist, kerberos


πŸ’œ AUTHOR πŸ’œ

MIT


1985-2025, MIT


and that's the whole page, bestie! this one came from MIT Kerberos, version 1.22.1 β€” go forth, destroy those tickets, and log off like the main character you are πŸ’–βœ¨πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from