aboutsummaryrefslogtreecommitdiff
path: root/crypto/krb5/doc/html/basic/rcache_def.html
diff options
context:
space:
mode:
Diffstat (limited to 'crypto/krb5/doc/html/basic/rcache_def.html')
-rw-r--r--crypto/krb5/doc/html/basic/rcache_def.html32
1 files changed, 15 insertions, 17 deletions
diff --git a/crypto/krb5/doc/html/basic/rcache_def.html b/crypto/krb5/doc/html/basic/rcache_def.html
index 3e8d53a4723c..3fa0a526dfc0 100644
--- a/crypto/krb5/doc/html/basic/rcache_def.html
+++ b/crypto/krb5/doc/html/basic/rcache_def.html
@@ -1,19 +1,17 @@
-
<!DOCTYPE html>
-<html>
+<html lang="en" data-content_root="../">
<head>
<meta charset="utf-8" />
- <meta name="viewport" content="width=device-width, initial-scale=1.0" /><meta name="generator" content="Docutils 0.17.1: http://docutils.sourceforge.net/" />
+ <meta name="viewport" content="width=device-width, initial-scale=1.0" /><meta name="viewport" content="width=device-width, initial-scale=1" />
<title>replay cache &#8212; MIT Kerberos Documentation</title>
- <link rel="stylesheet" type="text/css" href="../_static/pygments.css" />
- <link rel="stylesheet" type="text/css" href="../_static/agogo.css" />
- <link rel="stylesheet" type="text/css" href="../_static/kerb.css" />
- <script data-url_root="../" id="documentation_options" src="../_static/documentation_options.js"></script>
- <script src="../_static/jquery.js"></script>
- <script src="../_static/underscore.js"></script>
- <script src="../_static/doctools.js"></script>
+ <link rel="stylesheet" type="text/css" href="../_static/pygments.css?v=fa44fd50" />
+ <link rel="stylesheet" type="text/css" href="../_static/agogo.css?v=879f3c71" />
+ <link rel="stylesheet" type="text/css" href="../_static/kerb.css?v=6a0b3979" />
+ <script src="../_static/documentation_options.js?v=236fef3b"></script>
+ <script src="../_static/doctools.js?v=888ff710"></script>
+ <script src="../_static/sphinx_highlight.js?v=dc90522c"></script>
<link rel="author" title="About these documents" href="../about.html" />
<link rel="index" title="Index" href="../genindex.html" />
<link rel="search" title="Search" href="../search.html" />
@@ -53,7 +51,7 @@
<div class="body" role="main">
<section id="replay-cache">
-<span id="rcache-definition"></span><h1>replay cache<a class="headerlink" href="#replay-cache" title="Permalink to this headline">¶</a></h1>
+<span id="rcache-definition"></span><h1>replay cache<a class="headerlink" href="#replay-cache" title="Link to this heading">¶</a></h1>
<p>A replay cache (or “rcache”) keeps track of all authenticators
recently presented to a service. If a duplicate authentication
request is detected in the replay cache, an error message is sent to
@@ -63,7 +61,7 @@ the application program.</p>
indicate the type of replay cache and any associated cache naming
data to use.</p>
<section id="background-information">
-<h2>Background information<a class="headerlink" href="#background-information" title="Permalink to this headline">¶</a></h2>
+<h2>Background information<a class="headerlink" href="#background-information" title="Link to this heading">¶</a></h2>
<p>Some Kerberos or GSSAPI services use a simple authentication mechanism
where a message is sent containing an authenticator, which establishes
the encryption key that the client will use for talking to the
@@ -79,7 +77,7 @@ to cause the server to see the same messages again a second time. For
example, if the legitimate client sends “delete first message in
mailbox”, a replay from an attacker may delete another, different
“first” message. (Protocol design to guard against such problems has
-been discussed in <span class="target" id="index-0"></span><a class="rfc reference external" href="https://tools.ietf.org/html/rfc4120.html#section-10"><strong>RFC 4120#section-10</strong></a>.)</p>
+been discussed in <span class="target" id="index-0"></span><a class="rfc reference external" href="https://datatracker.ietf.org/doc/html/rfc4120.html#section-10"><strong>RFC 4120#section-10</strong></a>.)</p>
<p>Even if one protocol uses further protection to verify that the client
side of the connection actually knows the encryption keys (and thus is
presumably a legitimate user), if another service uses the same
@@ -103,7 +101,7 @@ authenticator triggers some interesting action in the service being
attacked.</p>
</section>
<section id="replay-cache-types">
-<h2>Replay cache types<a class="headerlink" href="#replay-cache-types" title="Permalink to this headline">¶</a></h2>
+<h2>Replay cache types<a class="headerlink" href="#replay-cache-types" title="Link to this heading">¶</a></h2>
<p>Unlike the credential cache and keytab interfaces, replay cache types
are in lowercase. The following types are defined:</p>
<ol class="arabic simple">
@@ -134,7 +132,7 @@ variable. The filename on Windows is <code class="docutils literal notranslate"
is opened normally.</p>
</section>
<section id="default-replay-cache-name">
-<h2>Default replay cache name<a class="headerlink" href="#default-replay-cache-name" title="Permalink to this headline">¶</a></h2>
+<h2>Default replay cache name<a class="headerlink" href="#default-replay-cache-name" title="Link to this heading">¶</a></h2>
<p>The default replay cache name is determined by the following, in
descending order of priority:</p>
<ol class="arabic simple">
@@ -207,8 +205,8 @@ set, the residual value is empty.</p></li>
<div class="footer-wrapper">
<div class="footer" >
- <div class="right" ><i>Release: 1.21.3</i><br />
- &copy; <a href="../copyright.html">Copyright</a> 1985-2024, MIT.
+ <div class="right" ><i>Release: 1.22-final</i><br />
+ &copy; <a href="../copyright.html">Copyright</a> 1985-2025, MIT.
</div>
<div class="left">