Provided by: krb5-user_1.10+dfsg~beta1-2_i386 bug


       kdestroy - destroy Kerberos tickets


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


       The  kdestroy utility destroys the user's active Kerberos authorization
       tickets by writing  zeros  to  the  specified  credentials  cache  that
       contains  them.  If the credentials cache is not specified, the default
       credentials cache is destroyed.


       -A     Destroys all caches in the collection, if a cache collection  is
              available.  -q Run quietly.  Normally kdestroy beeps if it fails
              to destroy the user's tickets.   The  -q  flag  suppresses  this

       -c cache_name
              use  cache_name  as  the  credentials  (ticket)  cache  name and
              location; 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 kdestroy command in
       your .logout file, so that your  tickets  are  destroyed  automatically
       when you log out.


       Kdestroy uses the following environment variables:

       KRB5CCNAME      Location of the default Kerberos 5 credentials (ticket)
                       cache, in the form type:residual.  If no type prefix is
                       present,  the  FILE  type  is assumed.  The type of the
                       default cache may determine the availability of a cache
                       collection;  for  instance, a default cache of type DIR
                       causes caches within the directory to be present in the


       /tmp/krb5cc_[uid]  default  location  of  Kerberos  5 credentials cache
                          ([uid] is the decimal UID of the user).


       kinit(1), klist(1), krb5(3)


       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.