xref: /illumos-gate/usr/src/man/man1/klist.1 (revision 6e6545bfaed3bab9ce836ee82d1abd8f2edba89a)
te
Copyright 1987, 1989 by the Student Information Processing Board of the Massachusetts Institute of Technology. For copying and distribution information, please see the file kerberosv5/mit-sipb-copyright.h.
Portions Copyright (c) 2004, Sun Microsystems, Inc. All Rights Reserved
The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
KLIST 1 "Nov 16, 2006"
NAME
klist - list currently held Kerberos tickets
SYNOPSIS

/usr/bin/klist [-e]
 [ [-c] [-f] [-s] [-a [-n]] [cache_name]]
 [-k [-t] [-K] [keytab_file]]
DESCRIPTION

The klist utility prints the name of the credentials cache, the identity of the principal that the tickets are for (as listed in the ticket file), and the principal names of all Kerberos tickets currently held by the user, along with the issue and expiration time for each authenticator. Principal names are listed in the form name/instance@realm, with the '/' omitted if the instance is not included, and the '@' omitted if the realm is not included.

If cache_file or keytab_name is not specified, klist displays the credentials in the default credentials cache or keytab files as appropriate. By default, your ticket is stored in the file /tmp/krb5cc_uid, where uid is the current user-ID of the user.

OPTIONS

The following options are supported: -a

Displays list of addresses in credentials. Uses the configured nameservice to translate numeric network addresses to the associated hostname if possible.

-c [cache_name]

Lists tickets held in a credentials cache. This is the default if neither -c nor -k is specified.

-e

Displays the encryption types of the session key and the ticket for each credential in the credential cache, or each key in the keytab file.

-f

Shows the flags present in the credentials, using the following abbreviations: a

Anonymous

A

Pre-authenticated

d

Post-dated

D

Post-dateable

f

Forwarded

F

Forwardable

H

Hardware authenticated

i

Invalid

I

Initial

O

Okay as delegate

p

Proxy

P

Proxiable

R

Renewable

T

Transit policy checked

-k [keytab_file]

List keys held in a keytab file.

-K

Displays the value of the encryption key in each keytab entry in the keytab file.

-n

Shows numeric IP addresses instead of reverse-resolving addresses. Only valid with -a option.

-s

Causes klist to run silently (produce no output), but to still set the exit status according to whether it finds the credentials cache. The exit status is 0 if klist finds a credentials cache, and `1if it does not, or if the local-realm TGT has expired.

-t

Displays the time entry timestamps for each keytab entry in the keytab file.

ENVIRONMENT VARIABLES

klist uses the following environment variable: KRB5CCNAME

Location of the credentials (ticket) cache. See krb5envvar(5) for syntax and details.

FILES
/tmp/krb5cc_uid

Default credentials cache (uid is the decimal UID of the user).

/etc/krb5/krb5.keytab

Default location for the local host's keytab file.

/etc/krb5/krb5.conf

Default location for the local host's configuration file. See krb5.conf(4).

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE ATTRIBUTE VALUE
Interface Stability See below.

The command arguments are Evolving. The command output is Unstable.

SEE ALSO

kdestroy(1), kinit(1), krb5.conf(4), attributes(5), krb5envvar(5), kerberos(5)

BUGS

When reading a file as a service key file, very little error checking is performed.