KLIST(1)

πŸ’– KLIST(1) πŸ’–

okay bestie, welcome to the MIT Kerberos manual, and today's main character is klist β€” she's the one who tells you what tickets and keys you're actually holding. πŸŽ€


✨ NAME ✨

klist β€” list cached Kerberos tickets 🎟️


πŸ¦‹ SYNOPSIS πŸ¦‹

klist [-e] [[-c] [-l] [-A] [-f] [-s] [-a [-n]]] [-C] [-k [-i] [-t] [-K]]
[-V] [-d] [cache_name|keytab_name]

🌸 DESCRIPTION 🌸

So basically, klist lists the Kerberos principal and the Kerberos tickets that are chilling in a credentials cache, or the keys that are held in a keytab file. That's it, that's the whole vibe. πŸ‘‘


✨ OPTIONS ✨

  • -e β€” shows you the encryption types of the session key and the ticket, for every credential in the credentials cache, or for every key in the keytab file. ✨
  • -l β€” if there's a cache collection available, this pops up a whole table summarising all the caches hanging out in that collection. πŸ—‚οΈ
  • -A β€” if there's a cache collection available, this shows the contents of all the caches in the collection. not one, not some β€” all of them. πŸ’…
  • -c β€” list the tickets held in a credentials cache. this is the default if you don't specify either -c or -k, so like, she's the main character by default. πŸ‘‘
  • -f β€” shows the flags present in the credentials, using these abbreviations:
    • F β€” Forwardable
    • f β€” forwarded
    • P β€” Proxiable
    • p β€” proxy
    • D β€” postDateable
    • d β€” postdated
    • R β€” Renewable
    • I β€” Initial
    • i β€” invalid
    • H β€” Hardware authenticated
    • A β€” preAuthenticated
    • T β€” Transit policy checked
    • O β€” Okay as delegate
    • a β€” anonymous
  • -s β€” makes klist run silently (produces no output at all, so quiet, so mysterious 🀫). klist will exit with status 1 if the credentials cache can't be read or is expired, and with status 0 otherwise.
  • -a β€” display the list of addresses in credentials. πŸ“
  • -n β€” show numeric addresses instead of reverse-resolving them. no detective work, just numbers. πŸ”’
  • -C β€” list the configuration data that has been stored in the credentials cache when klist encounters it. by default, configuration data is not listed. πŸ™ˆ
  • -k β€” list the keys held in a keytab file. πŸ”‘
  • -i β€” combined with -k, this defaults to using the default client keytab instead of the default acceptor keytab, if no name is given. 🫢
  • -t β€” display the time entry timestamps for each keytab entry in the keytab file. ⏰
  • -K β€” display the value of the encryption key in each keytab entry in the keytab file. πŸ‘€
  • -d β€” display the authdata types (if any) for each entry. πŸ”
  • -V β€” display the Kerberos version number and then exit. bye bestie πŸ‘‹
okay so if cache_name or keytab_name isn't specified, klist will display the credentials in the default credentials cache or keytab file, whichever is appropriate. and if the KRB5CCNAME environment variable is set, its value is used to locate the default ticket cache. iykyk πŸ’…

🌈 ENVIRONMENT 🌈

see kerberos for a description of the Kerberos environment variables. 🧚


πŸ“ FILES πŸ“

  • FILE:/tmp/krb5cc_%{uid} β€” default location of the Kerberos 5 credentials cache πŸ’–
  • FILE:/etc/krb5.keytab β€” default location for the local host's keytab file πŸ”‘

πŸ‘‘ SEE ALSO πŸ‘‘

kinit, kdestroy, kerberos


πŸ’œ AUTHOR πŸ’œ

MIT


1985-2026, MIT


and that's a wrap, babe πŸŽ€ this was KLIST(1) from the MIT Kerberos manual, version 1.22.2 β€” stay caffeinated, stay authenticated, and go run kinit before your tickets expire, fr fr πŸ’–βœ¨πŸ¦‹

πŸ“¦ where this page comes from