[1mSYNOPSIS[0m
[1mkdestroy [22m[[1m-A[22m] [[1m-q[22m] [[1m-c [4m[22mcache_name][0m
[1mDESCRIPTION[0m
The [4mkdestroy[24m utility destroys the user's active Kerberos authorization
tickets by writing zeros to the specified credentials cache that con-
tains them. If the credentials cache is not specified, the default
credentials cache is destroyed.
[1mOPTIONS[0m
[1m-A [22mDestroys all caches in the collection, if a cache collection is
available. [1m-q [22mRun quietly. Normally [1mkdestroy [22mbeeps if it fails
to destroy the user's tickets. The [1m-q [22mflag suppresses this
behavior.
[1m-c [4m[22mcache_name[0m
use [4mcache_name[24m as the credentials (ticket) cache name and loca-
tion; if this option is not used, the default cache name and
location are used.
The default credentials cache may vary between systems. If the
KRB5CCNAME environment variable is set, its value is used to
name the default ticket cache.
Most installations recommend that you place the [4mkdestroy[24m command in
your [4m.logout[24m file, so that your tickets are destroyed automatically
when you log out.
[1mENVIRONMENT[0m
[1mKdestroy [22muses the following environment variables:
KRB5CCNAME Location of the default Kerberos 5 credentials (ticket)
cache, in the form [4mtype[24m:[4mresidual[24m. If no type prefix is
present, the [1mFILE [22mtype is assumed. The type of the
default cache may determine the availability of a cache
collection; for instance, a default cache of type [1mDIR[0m
causes caches within the directory to be present in the
collection.
[1mFILES[0m
/tmp/krb5cc_[uid] default location of Kerberos 5 credentials cache
([uid] is the decimal UID of the user).
[1mSEE ALSO[0m
kinit(1), klist(1), krb5(3)
[1mBUGS[0m
Only the tickets in the specified credentials cache are destroyed.
Separate ticket caches are used to hold root instance and password
changing tickets. These should probably be destroyed too, or all of a
user's tickets kept in a single credentials cache.
Man(1) output converted with
man2html