xref: /freebsd/crypto/krb5/src/windows/leash/htmlhelp/html/KDESTROY.htm (revision 7f2fe78b9dd5f51c821d771b63d2e096f6fd49e9)
1<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
2<HTML>
3<HEAD>
4<meta name="GENERATOR" content="Microsoft&reg; HTML Help Workshop 4.1">
5<link rel="stylesheet" type="text/css" href="Leash.css" />
6
7<Title>KDESTROY</Title>
8</HEAD>
9<BODY>
10<H1>KDESTROY Command</H1>
11<table>
12<tr><th id="th2"> The following information reproduces the information from UNIX man page for the KDESTROY command.</th>
13</tr>
14</table>
15
16<H2>SYNOPSIS</H2>
17<table>
18<tr>
19<th id="th2">kdestroy</th>
20<td>
21<span class="command">[<B>-A</B>]    </span>
22<span class="command"> [<B>-q</B>]  </span>
23<span class="command">   [<B>-c</B> <I>cache</I><B>_</B><I>name]</I>   </span>
24
25</td>
26</tr>
27</table>
28
29
30<H2>DESCRIPTION</H2>
31<p>
32The  <I>kdestroy</I> utility destroys the user's active Kerberos
33authorization tickets by writing zeros to the specified
34credentials cache  that  contains  them.  If  the  credentials
35cache is not specified, the default credentials cache is
36destroyed.
37</P>
38
39<H2>OPTIONS</H2>
40<table>
41<tr>
42<th id="th2"><span class="command"> -A </span>  </th>
43<td>Destroys all caches in the collection, if a cache collection  is available. </td>
44<tr>
45<th id="th2"><span class="command"> -q </span></th>
46<td>Run quietly.  Normally <B>kdestroy</B> beeps if it fails to destroy the user's tickets.   The  <B>-q</B>  flag  suppresses  this behavior.
47</td>
48<tr>
49<th id="th2"> <span class="command"> -c</B=th> <I>cache</I><B>_</B><I>name</I></span></th>
50<td>Use  <span class="command"><I>cache</I><B>_</B><I>name</I></span> as the credentials (ticket) cache name and location; if this option is not used, the  default  cache  name  and location are used.<br>
51The  default credentials cache may vary between systems.  If the KRB5CCNAME environment variable is set, its  value  is  used  to
52name the default ticket cache.
53</td>
54</tr>
55</table>
56<p>
57 Most  installations  recommend  that  you place the <I>kdestroy</I> command
58in  your <I>.logout</I> file, so that your  tickets  are  destroyed  automatically
59when you log out.
60</p>
61
62<H2>ENVIRONMENT</H2>
63<p>
64<B>Kdestroy</B> uses the following environment variables:</p>
65
66<table>
67<tr>
68<th id="th2"> KRB5CCNAME</th>
69<td>      Location of the default Kerberos 5 credentials (ticket)
70                       cache, in the form <I>type</I>:<I>residual</I>.  If no type prefix is
71                       present,  the  <B>FILE</B>  type  is assumed.  The type of the
72                       default cache may determine the availability of a cache
73                       collection;  for  instance, a default cache of type <B>DIR</B>
74                       causes caches within the directory to be present in the
75                       collection. </td>
76</tr>
77</table>
78
79
80
81<H2>FILES</H2>
82<table>
83<tr>
84  <th id="th2">     <span class="command">   /tmp/krb5cc_[uid]  </span></th>
85<td>       default  location  of  Kerberos  5 credentials cache ([uid] is the decimal UID of the user). </td></tr>
86
87</table>
88
89
90<H2>SEE ALSO</H2>
91<ul id="helpul">
92<li><a href="HTML/KINIT.htm"><B>kinit(1)</B></a> </li>
93<li> <a href="HTML/KLIST.htm"><B>klist(1)</B></a></li>
94<li><B>krb5(3)</B></li>
95</ul>
96
97<H2>BUGS</H2><P>
98Only the tickets in the  specified  credentials  cache  are  destroyed.
99Separate  ticket  caches  are  used  to hold root instance and password
100changing tickets.  These should probably be destroyed too, or all of  a
101user's tickets kept in a single credentials cache.
102
103</P>
104
105
106
107</BODY>
108</HTML>
109