From: Tom Yu <tlyu@mit.edu>
Date: Tue, 9 Jan 2007 01:05:52 +0000 (+0000)
Subject: pull up r19035 from trunk
X-Git-Tag: krb5-1.6-final~6
X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=9d5fe074f6b2809ce5b4c42a71f4eaf7d75dff7e;p=krb5.git

pull up r19035 from trunk

 r19035@cathode-dark-space:  rra | 2007-01-04 17:32:41 -0500
 ticket: new
 Subject: Document KDC behavior without stash file
 Component: krb5-doc
 Version_Reported: 1.5.1
 Target_Version: 1.6
 Tags: pullup

 After the discussion of the optional stash file, document the effects of
 not creating a stash file.


ticket: 5271
version_fixed: 1.6

git-svn-id: svn://anonsvn.mit.edu/krb5/branches/krb5-1-6@19040 dc483132-0cff-0310-8789-dd5450dbe970
---

diff --git a/doc/install.texinfo b/doc/install.texinfo
index ebd64ce92..fb13a8192 100644
--- a/doc/install.texinfo
+++ b/doc/install.texinfo
@@ -461,6 +461,10 @@ 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.
 
+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.
+
 Note that @code{kdb5_util} will prompt you for the master key for the
 Kerberos database.  This key can be any string.  A good key is one you
 can remember, but that no one else can guess.  Examples of bad keys are