| 1 |
<!DOCTYPE html> |
| 2 |
|
| 3 |
<html lang="en" data-content_root="../"> |
| 4 |
<head> |
| 5 |
<meta charset="utf-8" /> |
| 6 |
<meta name="viewport" content="width=device-width, initial-scale=1.0" /><meta name="viewport" content="width=device-width, initial-scale=1" /> |
| 7 |
|
| 8 |
<title>Ticket management — MIT Kerberos Documentation</title> |
| 9 |
<link rel="stylesheet" type="text/css" href="../_static/pygments.css?v=fa44fd50" /> |
| 10 |
<link rel="stylesheet" type="text/css" href="../_static/agogo.css?v=879f3c71" /> |
| 11 |
<link rel="stylesheet" type="text/css" href="../_static/kerb.css?v=6a0b3979" /> |
| 12 |
<script src="../_static/documentation_options.js?v=6dbce55c"></script> |
| 13 |
<script src="../_static/doctools.js?v=888ff710"></script> |
| 14 |
<script src="../_static/sphinx_highlight.js?v=dc90522c"></script> |
| 15 |
<link rel="author" title="About these documents" href="../about.html" /> |
| 16 |
<link rel="index" title="Index" href="../genindex.html" /> |
| 17 |
<link rel="search" title="Search" href="../search.html" /> |
| 18 |
<link rel="copyright" title="Copyright" href="../copyright.html" /> |
| 19 |
<link rel="next" title="User config files" href="user_config/index.html" /> |
| 20 |
<link rel="prev" title="Password management" href="pwd_mgmt.html" /> |
| 21 |
</head><body> |
| 22 |
<div class="header-wrapper"> |
| 23 |
<div class="header"> |
| 24 |
|
| 25 |
|
| 26 |
<h1><a href="../index.html">MIT Kerberos Documentation</a></h1> |
| 27 |
|
| 28 |
<div class="rel"> |
| 29 |
|
| 30 |
<a href="../index.html" title="Full Table of Contents" |
| 31 |
accesskey="C">Contents</a> | |
| 32 |
<a href="pwd_mgmt.html" title="Password management" |
| 33 |
accesskey="P">previous</a> | |
| 34 |
<a href="user_config/index.html" title="User config files" |
| 35 |
accesskey="N">next</a> | |
| 36 |
<a href="../genindex.html" title="General Index" |
| 37 |
accesskey="I">index</a> | |
| 38 |
<a href="../search.html" title="Enter search criteria" |
| 39 |
accesskey="S">Search</a> | |
| 40 |
<a href="mailto:[email protected]?subject=Documentation__Ticket management">feedback</a> |
| 41 |
</div> |
| 42 |
</div> |
| 43 |
</div> |
| 44 |
|
| 45 |
<div class="content-wrapper"> |
| 46 |
<div class="content"> |
| 47 |
<div class="document"> |
| 48 |
|
| 49 |
<div class="documentwrapper"> |
| 50 |
<div class="bodywrapper"> |
| 51 |
<div class="body" role="main"> |
| 52 |
|
| 53 |
<section id="ticket-management"> |
| 54 |
<h1>Ticket management<a class="headerlink" href="#ticket-management" title="Link to this heading">¶</a></h1> |
| 55 |
<p>On many systems, Kerberos is built into the login program, and you get |
| 56 |
tickets automatically when you log in. Other programs, such as ssh, |
| 57 |
can forward copies of your tickets to a remote host. Most of these |
| 58 |
programs also automatically destroy your tickets when they exit. |
| 59 |
However, MIT recommends that you explicitly destroy your Kerberos |
| 60 |
tickets when you are through with them, just to be sure. One way to |
| 61 |
help ensure that this happens is to add the <a class="reference internal" href="user_commands/kdestroy.html#kdestroy-1"><span class="std std-ref">kdestroy</span></a> command |
| 62 |
to your .logout file. Additionally, if you are going to be away from |
| 63 |
your machine and are concerned about an intruder using your |
| 64 |
permissions, it is safest to either destroy all copies of your |
| 65 |
tickets, or use a screensaver that locks the screen.</p> |
| 66 |
<section id="kerberos-ticket-properties"> |
| 67 |
<h2>Kerberos ticket properties<a class="headerlink" href="#kerberos-ticket-properties" title="Link to this heading">¶</a></h2> |
| 68 |
<p>There are various properties that Kerberos tickets can have:</p> |
| 69 |
<p>If a ticket is <strong>forwardable</strong>, then the KDC can issue a new ticket |
| 70 |
(with a different network address, if necessary) based on the |
| 71 |
forwardable ticket. This allows for authentication forwarding without |
| 72 |
requiring a password to be typed in again. For example, if a user |
| 73 |
with a forwardable TGT logs into a remote system, the KDC could issue |
| 74 |
a new TGT for that user with the network address of the remote system, |
| 75 |
allowing authentication on that host to work as though the user were |
| 76 |
logged in locally.</p> |
| 77 |
<p>When the KDC creates a new ticket based on a forwardable ticket, it |
| 78 |
sets the <strong>forwarded</strong> flag on that new ticket. Any tickets that are |
| 79 |
created based on a ticket with the forwarded flag set will also have |
| 80 |
their forwarded flags set.</p> |
| 81 |
<p>A <strong>proxiable</strong> ticket is similar to a forwardable ticket in that it |
| 82 |
allows a service to take on the identity of the client. Unlike a |
| 83 |
forwardable ticket, however, a proxiable ticket is only issued for |
| 84 |
specific services. In other words, a ticket-granting ticket cannot be |
| 85 |
issued based on a ticket that is proxiable but not forwardable.</p> |
| 86 |
<p>A <strong>proxy</strong> ticket is one that was issued based on a proxiable ticket.</p> |
| 87 |
<p>A <strong>postdated</strong> ticket is issued with the invalid flag set. After the |
| 88 |
starting time listed on the ticket, it can be presented to the KDC to |
| 89 |
obtain valid tickets.</p> |
| 90 |
<p>Ticket-granting tickets with the <strong>postdateable</strong> flag set can be used |
| 91 |
to obtain postdated service tickets.</p> |
| 92 |
<p><strong>Renewable</strong> tickets can be used to obtain new session keys without |
| 93 |
the user entering their password again. A renewable ticket has two |
| 94 |
expiration times. The first is the time at which this particular |
| 95 |
ticket expires. The second is the latest possible expiration time for |
| 96 |
any ticket issued based on this renewable ticket.</p> |
| 97 |
<p>A ticket with the <strong>initial flag</strong> set was issued based on the |
| 98 |
authentication protocol, and not on a ticket-granting ticket. |
| 99 |
Application servers that wish to ensure that the user’s key has been |
| 100 |
recently presented for verification could specify that this flag must |
| 101 |
be set to accept the ticket.</p> |
| 102 |
<p>An <strong>invalid</strong> ticket must be rejected by application servers. |
| 103 |
Postdated tickets are usually issued with this flag set, and must be |
| 104 |
validated by the KDC before they can be used.</p> |
| 105 |
<p>A <strong>preauthenticated</strong> ticket is one that was only issued after the |
| 106 |
client requesting the ticket had authenticated itself to the KDC.</p> |
| 107 |
<p>The <strong>hardware authentication</strong> flag is set on a ticket which required |
| 108 |
the use of hardware for authentication. The hardware is expected to |
| 109 |
be possessed only by the client which requested the tickets.</p> |
| 110 |
<p>If a ticket has the <strong>transit policy</strong> checked flag set, then the KDC |
| 111 |
that issued this ticket implements the transited-realm check policy |
| 112 |
and checked the transited-realms list on the ticket. The |
| 113 |
transited-realms list contains a list of all intermediate realms |
| 114 |
between the realm of the KDC that issued the first ticket and that of |
| 115 |
the one that issued the current ticket. If this flag is not set, then |
| 116 |
the application server must check the transited realms itself or else |
| 117 |
reject the ticket.</p> |
| 118 |
<p>The <strong>okay as delegate</strong> flag indicates that the server specified in |
| 119 |
the ticket is suitable as a delegate as determined by the policy of |
| 120 |
that realm. Some client applications may use this flag to decide |
| 121 |
whether to forward tickets to a remote host, although many |
| 122 |
applications do not honor it.</p> |
| 123 |
<p>An <strong>anonymous</strong> ticket is one in which the named principal is a |
| 124 |
generic principal for that realm; it does not actually specify the |
| 125 |
individual that will be using the ticket. This ticket is meant only |
| 126 |
to securely distribute a session key.</p> |
| 127 |
</section> |
| 128 |
<section id="obtaining-tickets-with-kinit"> |
| 129 |
<span id="obtain-tkt"></span><h2>Obtaining tickets with kinit<a class="headerlink" href="#obtaining-tickets-with-kinit" title="Link to this heading">¶</a></h2> |
| 130 |
<p>If your site has integrated Kerberos V5 with the login system, you |
| 131 |
will get Kerberos tickets automatically when you log in. Otherwise, |
| 132 |
you may need to explicitly obtain your Kerberos tickets, using the |
| 133 |
<a class="reference internal" href="user_commands/kinit.html#kinit-1"><span class="std std-ref">kinit</span></a> program. Similarly, if your Kerberos tickets expire, |
| 134 |
use the kinit program to obtain new ones.</p> |
| 135 |
<p>To use the kinit program, simply type <code class="docutils literal notranslate"><span class="pre">kinit</span></code> and then type your |
| 136 |
password at the prompt. For example, Jennifer (whose username is |
| 137 |
<code class="docutils literal notranslate"><span class="pre">jennifer</span></code>) works for Bleep, Inc. (a fictitious company with the |
| 138 |
domain name mit.edu and the Kerberos realm ATHENA.MIT.EDU). She would |
| 139 |
type:</p> |
| 140 |
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">shell</span><span class="o">%</span> <span class="n">kinit</span> |
| 141 |
<span class="n">Password</span> <span class="k">for</span> <span class="n">jennifer</span><span class="nd">@ATHENA</span><span class="o">.</span><span class="n">MIT</span><span class="o">.</span><span class="n">EDU</span><span class="p">:</span> <span class="o"><--</span> <span class="p">[</span><span class="n">Type</span> <span class="n">jennifer</span><span class="s1">'s password here.]</span> |
| 142 |
<span class="n">shell</span><span class="o">%</span> |
| 143 |
</pre></div> |
| 144 |
</div> |
| 145 |
<p>If you type your password incorrectly, kinit will give you the |
| 146 |
following error message:</p> |
| 147 |
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">shell</span><span class="o">%</span> <span class="n">kinit</span> |
| 148 |
<span class="n">Password</span> <span class="k">for</span> <span class="n">jennifer</span><span class="nd">@ATHENA</span><span class="o">.</span><span class="n">MIT</span><span class="o">.</span><span class="n">EDU</span><span class="p">:</span> <span class="o"><--</span> <span class="p">[</span><span class="n">Type</span> <span class="n">the</span> <span class="n">wrong</span> <span class="n">password</span> <span class="n">here</span><span class="o">.</span><span class="p">]</span> |
| 149 |
<span class="n">kinit</span><span class="p">:</span> <span class="n">Password</span> <span class="n">incorrect</span> |
| 150 |
<span class="n">shell</span><span class="o">%</span> |
| 151 |
</pre></div> |
| 152 |
</div> |
| 153 |
<p>and you won’t get Kerberos tickets.</p> |
| 154 |
<p>By default, kinit assumes you want tickets for your own username in |
| 155 |
your default realm. Suppose Jennifer’s friend David is visiting, and |
| 156 |
he wants to borrow a window to check his mail. David needs to get |
| 157 |
tickets for himself in his own realm, EXAMPLE.COM. He would type:</p> |
| 158 |
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">shell</span><span class="o">%</span> <span class="n">kinit</span> <span class="n">david</span><span class="nd">@EXAMPLE</span><span class="o">.</span><span class="n">COM</span> |
| 159 |
<span class="n">Password</span> <span class="k">for</span> <span class="n">david</span><span class="nd">@EXAMPLE</span><span class="o">.</span><span class="n">COM</span><span class="p">:</span> <span class="o"><--</span> <span class="p">[</span><span class="n">Type</span> <span class="n">david</span><span class="s1">'s password here.]</span> |
| 160 |
<span class="n">shell</span><span class="o">%</span> |
| 161 |
</pre></div> |
| 162 |
</div> |
| 163 |
<p>David would then have tickets which he could use to log onto his own |
| 164 |
machine. Note that he typed his password locally on Jennifer’s |
| 165 |
machine, but it never went over the network. Kerberos on the local |
| 166 |
host performed the authentication to the KDC in the other realm.</p> |
| 167 |
<p>If you want to be able to forward your tickets to another host, you |
| 168 |
need to request forwardable tickets. You do this by specifying the |
| 169 |
<strong>-f</strong> option:</p> |
| 170 |
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">shell</span><span class="o">%</span> <span class="n">kinit</span> <span class="o">-</span><span class="n">f</span> |
| 171 |
<span class="n">Password</span> <span class="k">for</span> <span class="n">jennifer</span><span class="nd">@ATHENA</span><span class="o">.</span><span class="n">MIT</span><span class="o">.</span><span class="n">EDU</span><span class="p">:</span> <span class="o"><--</span> <span class="p">[</span><span class="n">Type</span> <span class="n">your</span> <span class="n">password</span> <span class="n">here</span><span class="o">.</span><span class="p">]</span> |
| 172 |
<span class="n">shell</span><span class="o">%</span> |
| 173 |
</pre></div> |
| 174 |
</div> |
| 175 |
<p>Note that kinit does not tell you that it obtained forwardable |
| 176 |
tickets; you can verify this using the <a class="reference internal" href="user_commands/klist.html#klist-1"><span class="std std-ref">klist</span></a> command (see |
| 177 |
<a class="reference internal" href="#view-tkt"><span class="std std-ref">Viewing tickets with klist</span></a>).</p> |
| 178 |
<p>Normally, your tickets are good for your system’s default ticket |
| 179 |
lifetime, which is ten hours on many systems. You can specify a |
| 180 |
different ticket lifetime with the <strong>-l</strong> option. Add the letter |
| 181 |
<strong>s</strong> to the value for seconds, <strong>m</strong> for minutes, <strong>h</strong> for hours, or |
| 182 |
<strong>d</strong> for days. For example, to obtain forwardable tickets for |
| 183 |
<code class="docutils literal notranslate"><span class="pre">david@EXAMPLE.COM</span></code> that would be good for three hours, you would |
| 184 |
type:</p> |
| 185 |
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">shell</span><span class="o">%</span> <span class="n">kinit</span> <span class="o">-</span><span class="n">f</span> <span class="o">-</span><span class="n">l</span> <span class="mi">3</span><span class="n">h</span> <span class="n">david</span><span class="nd">@EXAMPLE</span><span class="o">.</span><span class="n">COM</span> |
| 186 |
<span class="n">Password</span> <span class="k">for</span> <span class="n">david</span><span class="nd">@EXAMPLE</span><span class="o">.</span><span class="n">COM</span><span class="p">:</span> <span class="o"><--</span> <span class="p">[</span><span class="n">Type</span> <span class="n">david</span><span class="s1">'s password here.]</span> |
| 187 |
<span class="n">shell</span><span class="o">%</span> |
| 188 |
</pre></div> |
| 189 |
</div> |
| 190 |
<div class="admonition note"> |
| 191 |
<p class="admonition-title">Note</p> |
| 192 |
<p>You cannot mix units; specifying a lifetime of 3h30m would |
| 193 |
result in an error. Note also that most systems specify a |
| 194 |
maximum ticket lifetime. If you request a longer ticket |
| 195 |
lifetime, it will be automatically truncated to the maximum |
| 196 |
lifetime.</p> |
| 197 |
</div> |
| 198 |
</section> |
| 199 |
<section id="viewing-tickets-with-klist"> |
| 200 |
<span id="view-tkt"></span><h2>Viewing tickets with klist<a class="headerlink" href="#viewing-tickets-with-klist" title="Link to this heading">¶</a></h2> |
| 201 |
<p>The <a class="reference internal" href="user_commands/klist.html#klist-1"><span class="std std-ref">klist</span></a> command shows your tickets. When you first obtain |
| 202 |
tickets, you will have only the ticket-granting ticket. The listing |
| 203 |
would look like this:</p> |
| 204 |
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">shell</span><span class="o">%</span> <span class="n">klist</span> |
| 205 |
<span class="n">Ticket</span> <span class="n">cache</span><span class="p">:</span> <span class="o">/</span><span class="n">tmp</span><span class="o">/</span><span class="n">krb5cc_ttypa</span> |
| 206 |
<span class="n">Default</span> <span class="n">principal</span><span class="p">:</span> <span class="n">jennifer</span><span class="nd">@ATHENA</span><span class="o">.</span><span class="n">MIT</span><span class="o">.</span><span class="n">EDU</span> |
| 207 |
|
| 208 |
<span class="n">Valid</span> <span class="n">starting</span> <span class="n">Expires</span> <span class="n">Service</span> <span class="n">principal</span> |
| 209 |
<span class="mi">06</span><span class="o">/</span><span class="mi">07</span><span class="o">/</span><span class="mi">04</span> <span class="mi">19</span><span class="p">:</span><span class="mi">49</span><span class="p">:</span><span class="mi">21</span> <span class="mi">06</span><span class="o">/</span><span class="mi">08</span><span class="o">/</span><span class="mi">04</span> <span class="mi">05</span><span class="p">:</span><span class="mi">49</span><span class="p">:</span><span class="mi">19</span> <span class="n">krbtgt</span><span class="o">/</span><span class="n">ATHENA</span><span class="o">.</span><span class="n">MIT</span><span class="o">.</span><span class="n">EDU</span><span class="nd">@ATHENA</span><span class="o">.</span><span class="n">MIT</span><span class="o">.</span><span class="n">EDU</span> |
| 210 |
<span class="n">shell</span><span class="o">%</span> |
| 211 |
</pre></div> |
| 212 |
</div> |
| 213 |
<p>The ticket cache is the location of your ticket file. In the above |
| 214 |
example, this file is named <code class="docutils literal notranslate"><span class="pre">/tmp/krb5cc_ttypa</span></code>. The default |
| 215 |
principal is your Kerberos principal.</p> |
| 216 |
<p>The “valid starting” and “expires” fields describe the period of time |
| 217 |
during which the ticket is valid. The “service principal” describes |
| 218 |
each ticket. The ticket-granting ticket has a first component |
| 219 |
<code class="docutils literal notranslate"><span class="pre">krbtgt</span></code>, and a second component which is the realm name.</p> |
| 220 |
<p>Now, if <code class="docutils literal notranslate"><span class="pre">jennifer</span></code> connected to the machine <code class="docutils literal notranslate"><span class="pre">daffodil.mit.edu</span></code>, |
| 221 |
and then typed “klist” again, she would have gotten the following |
| 222 |
result:</p> |
| 223 |
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">shell</span><span class="o">%</span> <span class="n">klist</span> |
| 224 |
<span class="n">Ticket</span> <span class="n">cache</span><span class="p">:</span> <span class="o">/</span><span class="n">tmp</span><span class="o">/</span><span class="n">krb5cc_ttypa</span> |
| 225 |
<span class="n">Default</span> <span class="n">principal</span><span class="p">:</span> <span class="n">jennifer</span><span class="nd">@ATHENA</span><span class="o">.</span><span class="n">MIT</span><span class="o">.</span><span class="n">EDU</span> |
| 226 |
|
| 227 |
<span class="n">Valid</span> <span class="n">starting</span> <span class="n">Expires</span> <span class="n">Service</span> <span class="n">principal</span> |
| 228 |
<span class="mi">06</span><span class="o">/</span><span class="mi">07</span><span class="o">/</span><span class="mi">04</span> <span class="mi">19</span><span class="p">:</span><span class="mi">49</span><span class="p">:</span><span class="mi">21</span> <span class="mi">06</span><span class="o">/</span><span class="mi">08</span><span class="o">/</span><span class="mi">04</span> <span class="mi">05</span><span class="p">:</span><span class="mi">49</span><span class="p">:</span><span class="mi">19</span> <span class="n">krbtgt</span><span class="o">/</span><span class="n">ATHENA</span><span class="o">.</span><span class="n">MIT</span><span class="o">.</span><span class="n">EDU</span><span class="nd">@ATHENA</span><span class="o">.</span><span class="n">MIT</span><span class="o">.</span><span class="n">EDU</span> |
| 229 |
<span class="mi">06</span><span class="o">/</span><span class="mi">07</span><span class="o">/</span><span class="mi">04</span> <span class="mi">20</span><span class="p">:</span><span class="mi">22</span><span class="p">:</span><span class="mi">30</span> <span class="mi">06</span><span class="o">/</span><span class="mi">08</span><span class="o">/</span><span class="mi">04</span> <span class="mi">05</span><span class="p">:</span><span class="mi">49</span><span class="p">:</span><span class="mi">19</span> <span class="n">host</span><span class="o">/</span><span class="n">daffodil</span><span class="o">.</span><span class="n">mit</span><span class="o">.</span><span class="n">edu</span><span class="nd">@ATHENA</span><span class="o">.</span><span class="n">MIT</span><span class="o">.</span><span class="n">EDU</span> |
| 230 |
<span class="n">shell</span><span class="o">%</span> |
| 231 |
</pre></div> |
| 232 |
</div> |
| 233 |
<p>Here’s what happened: when <code class="docutils literal notranslate"><span class="pre">jennifer</span></code> used ssh to connect to the |
| 234 |
host <code class="docutils literal notranslate"><span class="pre">daffodil.mit.edu</span></code>, the ssh program presented her |
| 235 |
ticket-granting ticket to the KDC and requested a host ticket for the |
| 236 |
host <code class="docutils literal notranslate"><span class="pre">daffodil.mit.edu</span></code>. The KDC sent the host ticket, which ssh |
| 237 |
then presented to the host <code class="docutils literal notranslate"><span class="pre">daffodil.mit.edu</span></code>, and she was allowed |
| 238 |
to log in without typing her password.</p> |
| 239 |
<p>Suppose your Kerberos tickets allow you to log into a host in another |
| 240 |
domain, such as <code class="docutils literal notranslate"><span class="pre">trillium.example.com</span></code>, which is also in another |
| 241 |
Kerberos realm, <code class="docutils literal notranslate"><span class="pre">EXAMPLE.COM</span></code>. If you ssh to this host, you will |
| 242 |
receive a ticket-granting ticket for the realm <code class="docutils literal notranslate"><span class="pre">EXAMPLE.COM</span></code>, plus |
| 243 |
the new host ticket for <code class="docutils literal notranslate"><span class="pre">trillium.example.com</span></code>. klist will now |
| 244 |
show:</p> |
| 245 |
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">shell</span><span class="o">%</span> <span class="n">klist</span> |
| 246 |
<span class="n">Ticket</span> <span class="n">cache</span><span class="p">:</span> <span class="o">/</span><span class="n">tmp</span><span class="o">/</span><span class="n">krb5cc_ttypa</span> |
| 247 |
<span class="n">Default</span> <span class="n">principal</span><span class="p">:</span> <span class="n">jennifer</span><span class="nd">@ATHENA</span><span class="o">.</span><span class="n">MIT</span><span class="o">.</span><span class="n">EDU</span> |
| 248 |
|
| 249 |
<span class="n">Valid</span> <span class="n">starting</span> <span class="n">Expires</span> <span class="n">Service</span> <span class="n">principal</span> |
| 250 |
<span class="mi">06</span><span class="o">/</span><span class="mi">07</span><span class="o">/</span><span class="mi">04</span> <span class="mi">19</span><span class="p">:</span><span class="mi">49</span><span class="p">:</span><span class="mi">21</span> <span class="mi">06</span><span class="o">/</span><span class="mi">08</span><span class="o">/</span><span class="mi">04</span> <span class="mi">05</span><span class="p">:</span><span class="mi">49</span><span class="p">:</span><span class="mi">19</span> <span class="n">krbtgt</span><span class="o">/</span><span class="n">ATHENA</span><span class="o">.</span><span class="n">MIT</span><span class="o">.</span><span class="n">EDU</span><span class="nd">@ATHENA</span><span class="o">.</span><span class="n">MIT</span><span class="o">.</span><span class="n">EDU</span> |
| 251 |
<span class="mi">06</span><span class="o">/</span><span class="mi">07</span><span class="o">/</span><span class="mi">04</span> <span class="mi">20</span><span class="p">:</span><span class="mi">22</span><span class="p">:</span><span class="mi">30</span> <span class="mi">06</span><span class="o">/</span><span class="mi">08</span><span class="o">/</span><span class="mi">04</span> <span class="mi">05</span><span class="p">:</span><span class="mi">49</span><span class="p">:</span><span class="mi">19</span> <span class="n">host</span><span class="o">/</span><span class="n">daffodil</span><span class="o">.</span><span class="n">mit</span><span class="o">.</span><span class="n">edu</span><span class="nd">@ATHENA</span><span class="o">.</span><span class="n">MIT</span><span class="o">.</span><span class="n">EDU</span> |
| 252 |
<span class="mi">06</span><span class="o">/</span><span class="mi">07</span><span class="o">/</span><span class="mi">04</span> <span class="mi">20</span><span class="p">:</span><span class="mi">24</span><span class="p">:</span><span class="mi">18</span> <span class="mi">06</span><span class="o">/</span><span class="mi">08</span><span class="o">/</span><span class="mi">04</span> <span class="mi">05</span><span class="p">:</span><span class="mi">49</span><span class="p">:</span><span class="mi">19</span> <span class="n">krbtgt</span><span class="o">/</span><span class="n">EXAMPLE</span><span class="o">.</span><span class="n">COM</span><span class="nd">@ATHENA</span><span class="o">.</span><span class="n">MIT</span><span class="o">.</span><span class="n">EDU</span> |
| 253 |
<span class="mi">06</span><span class="o">/</span><span class="mi">07</span><span class="o">/</span><span class="mi">04</span> <span class="mi">20</span><span class="p">:</span><span class="mi">24</span><span class="p">:</span><span class="mi">18</span> <span class="mi">06</span><span class="o">/</span><span class="mi">08</span><span class="o">/</span><span class="mi">04</span> <span class="mi">05</span><span class="p">:</span><span class="mi">49</span><span class="p">:</span><span class="mi">19</span> <span class="n">host</span><span class="o">/</span><span class="n">trillium</span><span class="o">.</span><span class="n">example</span><span class="o">.</span><span class="n">com</span><span class="nd">@EXAMPLE</span><span class="o">.</span><span class="n">COM</span> |
| 254 |
<span class="n">shell</span><span class="o">%</span> |
| 255 |
</pre></div> |
| 256 |
</div> |
| 257 |
<p>Depending on your host’s and realm’s configuration, you may also see a |
| 258 |
ticket with the service principal <code class="docutils literal notranslate"><span class="pre">host/trillium.example.com@</span></code>. If |
| 259 |
so, this means that your host did not know what realm |
| 260 |
trillium.example.com is in, so it asked the <code class="docutils literal notranslate"><span class="pre">ATHENA.MIT.EDU</span></code> KDC for |
| 261 |
a referral. The next time you connect to <code class="docutils literal notranslate"><span class="pre">trillium.example.com</span></code>, |
| 262 |
the odd-looking entry will be used to avoid needing to ask for a |
| 263 |
referral again.</p> |
| 264 |
<p>You can use the <strong>-f</strong> option to view the flags that apply to your |
| 265 |
tickets. The flags are:</p> |
| 266 |
<table class="docutils align-default"> |
| 267 |
<tbody> |
| 268 |
<tr class="row-odd"><td><p>F</p></td> |
| 269 |
<td><p>Forwardable</p></td> |
| 270 |
</tr> |
| 271 |
<tr class="row-even"><td><p>f</p></td> |
| 272 |
<td><p>forwarded</p></td> |
| 273 |
</tr> |
| 274 |
<tr class="row-odd"><td><p>P</p></td> |
| 275 |
<td><p>Proxiable</p></td> |
| 276 |
</tr> |
| 277 |
<tr class="row-even"><td><p>p</p></td> |
| 278 |
<td><p>proxy</p></td> |
| 279 |
</tr> |
| 280 |
<tr class="row-odd"><td><p>D</p></td> |
| 281 |
<td><p>postDateable</p></td> |
| 282 |
</tr> |
| 283 |
<tr class="row-even"><td><p>d</p></td> |
| 284 |
<td><p>postdated</p></td> |
| 285 |
</tr> |
| 286 |
<tr class="row-odd"><td><p>R</p></td> |
| 287 |
<td><p>Renewable</p></td> |
| 288 |
</tr> |
| 289 |
<tr class="row-even"><td><p>I</p></td> |
| 290 |
<td><p>Initial</p></td> |
| 291 |
</tr> |
| 292 |
<tr class="row-odd"><td><p>i</p></td> |
| 293 |
<td><p>invalid</p></td> |
| 294 |
</tr> |
| 295 |
<tr class="row-even"><td><p>H</p></td> |
| 296 |
<td><p>Hardware authenticated</p></td> |
| 297 |
</tr> |
| 298 |
<tr class="row-odd"><td><p>A</p></td> |
| 299 |
<td><p>preAuthenticated</p></td> |
| 300 |
</tr> |
| 301 |
<tr class="row-even"><td><p>T</p></td> |
| 302 |
<td><p>Transit policy checked</p></td> |
| 303 |
</tr> |
| 304 |
<tr class="row-odd"><td><p>O</p></td> |
| 305 |
<td><p>Okay as delegate</p></td> |
| 306 |
</tr> |
| 307 |
<tr class="row-even"><td><p>a</p></td> |
| 308 |
<td><p>anonymous</p></td> |
| 309 |
</tr> |
| 310 |
</tbody> |
| 311 |
</table> |
| 312 |
<p>Here is a sample listing. In this example, the user <em>jennifer</em> |
| 313 |
obtained her initial tickets (<strong>I</strong>), which are forwardable (<strong>F</strong>) |
| 314 |
and postdated (<strong>d</strong>) but not yet validated (<strong>i</strong>):</p> |
| 315 |
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">shell</span><span class="o">%</span> <span class="n">klist</span> <span class="o">-</span><span class="n">f</span> |
| 316 |
<span class="n">Ticket</span> <span class="n">cache</span><span class="p">:</span> <span class="o">/</span><span class="n">tmp</span><span class="o">/</span><span class="n">krb5cc_320</span> |
| 317 |
<span class="n">Default</span> <span class="n">principal</span><span class="p">:</span> <span class="n">jennifer</span><span class="nd">@ATHENA</span><span class="o">.</span><span class="n">MIT</span><span class="o">.</span><span class="n">EDU</span> |
| 318 |
|
| 319 |
<span class="n">Valid</span> <span class="n">starting</span> <span class="n">Expires</span> <span class="n">Service</span> <span class="n">principal</span> |
| 320 |
<span class="mi">31</span><span class="o">/</span><span class="mi">07</span><span class="o">/</span><span class="mi">05</span> <span class="mi">19</span><span class="p">:</span><span class="mi">06</span><span class="p">:</span><span class="mi">25</span> <span class="mi">31</span><span class="o">/</span><span class="mi">07</span><span class="o">/</span><span class="mi">05</span> <span class="mi">19</span><span class="p">:</span><span class="mi">16</span><span class="p">:</span><span class="mi">25</span> <span class="n">krbtgt</span><span class="o">/</span><span class="n">ATHENA</span><span class="o">.</span><span class="n">MIT</span><span class="o">.</span><span class="n">EDU</span><span class="nd">@ATHENA</span><span class="o">.</span><span class="n">MIT</span><span class="o">.</span><span class="n">EDU</span> |
| 321 |
<span class="n">Flags</span><span class="p">:</span> <span class="n">FdiI</span> |
| 322 |
<span class="n">shell</span><span class="o">%</span> |
| 323 |
</pre></div> |
| 324 |
</div> |
| 325 |
<p>In the following example, the user <em>david</em>’s tickets were forwarded |
| 326 |
(<strong>f</strong>) to this host from another host. The tickets are reforwardable |
| 327 |
(<strong>F</strong>):</p> |
| 328 |
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">shell</span><span class="o">%</span> <span class="n">klist</span> <span class="o">-</span><span class="n">f</span> |
| 329 |
<span class="n">Ticket</span> <span class="n">cache</span><span class="p">:</span> <span class="o">/</span><span class="n">tmp</span><span class="o">/</span><span class="n">krb5cc_p11795</span> |
| 330 |
<span class="n">Default</span> <span class="n">principal</span><span class="p">:</span> <span class="n">david</span><span class="nd">@EXAMPLE</span><span class="o">.</span><span class="n">COM</span> |
| 331 |
|
| 332 |
<span class="n">Valid</span> <span class="n">starting</span> <span class="n">Expires</span> <span class="n">Service</span> <span class="n">principal</span> |
| 333 |
<span class="mi">07</span><span class="o">/</span><span class="mi">31</span><span class="o">/</span><span class="mi">05</span> <span class="mi">11</span><span class="p">:</span><span class="mi">52</span><span class="p">:</span><span class="mi">29</span> <span class="mi">07</span><span class="o">/</span><span class="mi">31</span><span class="o">/</span><span class="mi">05</span> <span class="mi">21</span><span class="p">:</span><span class="mi">11</span><span class="p">:</span><span class="mi">23</span> <span class="n">krbtgt</span><span class="o">/</span><span class="n">EXAMPLE</span><span class="o">.</span><span class="n">COM</span><span class="nd">@EXAMPLE</span><span class="o">.</span><span class="n">COM</span> |
| 334 |
<span class="n">Flags</span><span class="p">:</span> <span class="n">Ff</span> |
| 335 |
<span class="mi">07</span><span class="o">/</span><span class="mi">31</span><span class="o">/</span><span class="mi">05</span> <span class="mi">12</span><span class="p">:</span><span class="mi">03</span><span class="p">:</span><span class="mi">48</span> <span class="mi">07</span><span class="o">/</span><span class="mi">31</span><span class="o">/</span><span class="mi">05</span> <span class="mi">21</span><span class="p">:</span><span class="mi">11</span><span class="p">:</span><span class="mi">23</span> <span class="n">host</span><span class="o">/</span><span class="n">trillium</span><span class="o">.</span><span class="n">example</span><span class="o">.</span><span class="n">com</span><span class="nd">@EXAMPLE</span><span class="o">.</span><span class="n">COM</span> |
| 336 |
<span class="n">Flags</span><span class="p">:</span> <span class="n">Ff</span> |
| 337 |
<span class="n">shell</span><span class="o">%</span> |
| 338 |
</pre></div> |
| 339 |
</div> |
| 340 |
</section> |
| 341 |
<section id="destroying-tickets-with-kdestroy"> |
| 342 |
<h2>Destroying tickets with kdestroy<a class="headerlink" href="#destroying-tickets-with-kdestroy" title="Link to this heading">¶</a></h2> |
| 343 |
<p>Your Kerberos tickets are proof that you are indeed yourself, and |
| 344 |
tickets could be stolen if someone gains access to a computer where |
| 345 |
they are stored. If this happens, the person who has them can |
| 346 |
masquerade as you until they expire. For this reason, you should |
| 347 |
destroy your Kerberos tickets when you are away from your computer.</p> |
| 348 |
<p>Destroying your tickets is easy. Simply type kdestroy:</p> |
| 349 |
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">shell</span><span class="o">%</span> <span class="n">kdestroy</span> |
| 350 |
<span class="n">shell</span><span class="o">%</span> |
| 351 |
</pre></div> |
| 352 |
</div> |
| 353 |
<p>If <a class="reference internal" href="user_commands/kdestroy.html#kdestroy-1"><span class="std std-ref">kdestroy</span></a> fails to destroy your tickets, it will beep and |
| 354 |
give an error message. For example, if kdestroy can’t find any |
| 355 |
tickets to destroy, it will give the following message:</p> |
| 356 |
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">shell</span><span class="o">%</span> <span class="n">kdestroy</span> |
| 357 |
<span class="n">kdestroy</span><span class="p">:</span> <span class="n">No</span> <span class="n">credentials</span> <span class="n">cache</span> <span class="n">file</span> <span class="n">found</span> <span class="k">while</span> <span class="n">destroying</span> <span class="n">cache</span> |
| 358 |
<span class="n">shell</span><span class="o">%</span> |
| 359 |
</pre></div> |
| 360 |
</div> |
| 361 |
</section> |
| 362 |
</section> |
| 363 |
|
| 364 |
|
| 365 |
<div class="clearer"></div> |
| 366 |
</div> |
| 367 |
</div> |
| 368 |
</div> |
| 369 |
</div> |
| 370 |
<div class="sidebar"> |
| 371 |
|
| 372 |
<h2>On this page</h2> |
| 373 |
<ul> |
| 374 |
<li><a class="reference internal" href="#">Ticket management</a><ul> |
| 375 |
<li><a class="reference internal" href="#kerberos-ticket-properties">Kerberos ticket properties</a></li> |
| 376 |
<li><a class="reference internal" href="#obtaining-tickets-with-kinit">Obtaining tickets with kinit</a></li> |
| 377 |
<li><a class="reference internal" href="#viewing-tickets-with-klist">Viewing tickets with klist</a></li> |
| 378 |
<li><a class="reference internal" href="#destroying-tickets-with-kdestroy">Destroying tickets with kdestroy</a></li> |
| 379 |
</ul> |
| 380 |
</li> |
| 381 |
</ul> |
| 382 |
|
| 383 |
<br/> |
| 384 |
<h2>Table of contents</h2> |
| 385 |
<ul class="current"> |
| 386 |
<li class="toctree-l1 current"><a class="reference internal" href="index.html">For users</a><ul class="current"> |
| 387 |
<li class="toctree-l2"><a class="reference internal" href="pwd_mgmt.html">Password management</a></li> |
| 388 |
<li class="toctree-l2 current"><a class="current reference internal" href="#">Ticket management</a></li> |
| 389 |
<li class="toctree-l2"><a class="reference internal" href="user_config/index.html">User config files</a></li> |
| 390 |
<li class="toctree-l2"><a class="reference internal" href="user_commands/index.html">User commands</a></li> |
| 391 |
</ul> |
| 392 |
</li> |
| 393 |
<li class="toctree-l1"><a class="reference internal" href="../admin/index.html">For administrators</a></li> |
| 394 |
<li class="toctree-l1"><a class="reference internal" href="../appdev/index.html">For application developers</a></li> |
| 395 |
<li class="toctree-l1"><a class="reference internal" href="../plugindev/index.html">For plugin module developers</a></li> |
| 396 |
<li class="toctree-l1"><a class="reference internal" href="../build/index.html">Building Kerberos V5</a></li> |
| 397 |
<li class="toctree-l1"><a class="reference internal" href="../basic/index.html">Kerberos V5 concepts</a></li> |
| 398 |
<li class="toctree-l1"><a class="reference internal" href="../formats/index.html">Protocols and file formats</a></li> |
| 399 |
<li class="toctree-l1"><a class="reference internal" href="../mitK5features.html">MIT Kerberos features</a></li> |
| 400 |
<li class="toctree-l1"><a class="reference internal" href="../build_this.html">How to build this documentation from the source</a></li> |
| 401 |
<li class="toctree-l1"><a class="reference internal" href="../about.html">Contributing to the MIT Kerberos Documentation</a></li> |
| 402 |
<li class="toctree-l1"><a class="reference internal" href="../resources.html">Resources</a></li> |
| 403 |
</ul> |
| 404 |
|
| 405 |
<br/> |
| 406 |
<h4><a href="../index.html">Full Table of Contents</a></h4> |
| 407 |
<h4>Search</h4> |
| 408 |
<form class="search" action="../search.html" method="get"> |
| 409 |
<input type="text" name="q" size="18" /> |
| 410 |
<input type="submit" value="Go" /> |
| 411 |
<input type="hidden" name="check_keywords" value="yes" /> |
| 412 |
<input type="hidden" name="area" value="default" /> |
| 413 |
</form> |
| 414 |
|
| 415 |
</div> |
| 416 |
<div class="clearer"></div> |
| 417 |
</div> |
| 418 |
</div> |
| 419 |
|
| 420 |
<div class="footer-wrapper"> |
| 421 |
<div class="footer" > |
| 422 |
<div class="right" ><i>Release: 1.22.1</i><br /> |
| 423 |
© <a href="../copyright.html">Copyright</a> 1985-2025, MIT. |
| 424 |
</div> |
| 425 |
<div class="left"> |
| 426 |
|
| 427 |
<a href="../index.html" title="Full Table of Contents" |
| 428 |
>Contents</a> | |
| 429 |
<a href="pwd_mgmt.html" title="Password management" |
| 430 |
>previous</a> | |
| 431 |
<a href="user_config/index.html" title="User config files" |
| 432 |
>next</a> | |
| 433 |
<a href="../genindex.html" title="General Index" |
| 434 |
>index</a> | |
| 435 |
<a href="../search.html" title="Enter search criteria" |
| 436 |
>Search</a> | |
| 437 |
<a href="mailto:[email protected]?subject=Documentation__Ticket management">feedback</a> |
| 438 |
</div> |
| 439 |
</div> |
| 440 |
</div> |
| 441 |
|
| 442 |
</body> |
| 443 |
</html> |