aboutsummaryrefslogtreecommitdiff
path: root/crypto/krb5/doc/html/_sources/basic/stash_file_def.rst.txt
diff options
context:
space:
mode:
Diffstat (limited to 'crypto/krb5/doc/html/_sources/basic/stash_file_def.rst.txt')
-rw-r--r--crypto/krb5/doc/html/_sources/basic/stash_file_def.rst.txt25
1 files changed, 0 insertions, 25 deletions
diff --git a/crypto/krb5/doc/html/_sources/basic/stash_file_def.rst.txt b/crypto/krb5/doc/html/_sources/basic/stash_file_def.rst.txt
deleted file mode 100644
index 256e2c272d8d..000000000000
--- a/crypto/krb5/doc/html/_sources/basic/stash_file_def.rst.txt
+++ /dev/null
@@ -1,25 +0,0 @@
-.. _stash_definition:
-
-
-stash file
-============
-
-The stash file is a local copy of the master key that resides in
-encrypted form on the KDC's local disk. The stash file is used to
-authenticate the KDC to itself automatically before starting the
-:ref:`kadmind(8)` and :ref:`krb5kdc(8)` daemons (e.g., as part of the
-machine's boot sequence). The stash file, like the keytab file (see
-:ref:`keytab_file`) is a potential point-of-entry for a break-in, and
-if compromised, would allow unrestricted access to the Kerberos
-database. If you choose to install a stash file, it should be
-readable only by root, and should exist only on the KDC's local disk.
-The file should not be part of any backup of the machine, unless
-access to the backup data is secured as tightly as access to the
-master password itself.
-
-.. note::
-
- If you choose not to install a stash file, the KDC will prompt you for the master key each time it starts up.
- This means that the KDC will not be able to start automatically, such as after a system reboot.
-
-