summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorhin <hin@openbsd.org>2001-06-29 02:06:11 +0000
committerhin <hin@openbsd.org>2001-06-29 02:06:11 +0000
commit11e3ce161053473a76612d8d6963b72b14dc5e92 (patch)
tree7990085e69b037f3f792aeafbeb50cab8e4ebcff
parentuse mktemp for temporary files creation, remove unnecessary directory (diff)
downloadwireguard-openbsd-11e3ce161053473a76612d8d6963b72b14dc5e92.tar.xz
wireguard-openbsd-11e3ce161053473a76612d8d6963b72b14dc5e92.zip
/etc/krb5.conf -> /etc/kerberosV/krb5.conf
-rw-r--r--kerberosV/src/doc/setup.texi8
1 files changed, 4 insertions, 4 deletions
diff --git a/kerberosV/src/doc/setup.texi b/kerberosV/src/doc/setup.texi
index 14491f72445..25d4029b549 100644
--- a/kerberosV/src/doc/setup.texi
+++ b/kerberosV/src/doc/setup.texi
@@ -27,7 +27,7 @@ doing so. It will make life easier for you and everyone else.
@section Configuration file
To setup a realm you will first have to create a configuration file:
-@file{/etc/krb5.conf}. The @file{krb5.conf} file can contain many
+@file{/etc/kerberosV/krb5.conf}. The @file{krb5.conf} file can contain many
configuration options, some of which are described here.
There is a sample @file{krb5.conf} supplied with the distribution.
@@ -251,7 +251,7 @@ some defense against off-line attacks). To ensure that the users choose
good passwords, you can enable password quality controls in
@samp{kpasswdd}. The controls themselves are done in a shared library
that is used by @samp{kpasswdd}. To configure in these controls, add
-lines similar to the following to your @file{/etc/krb5.conf}:
+lines similar to the following to your @file{/etc/kerberosV/krb5.conf}:
@example
[password_quality]
@@ -307,7 +307,7 @@ Every slave needs a keytab with a principal,
@pindex ktutil
@code{ktutil} command and start
@pindex hpropd
-@code{propd}, as follows:
+@code{hpropd}, as follows:
@example
slave# ktutil get -p foo/admin host/`hostname`
@@ -337,7 +337,7 @@ automate this you will want to start
Starting the propagation once an hour from @code{cron} is probably a
good idea.
-@node Incremental propagation, Salting , Slave Servers, Setting up a realm
+f@node Incremental propagation, Salting , Slave Servers, Setting up a realm
@section Incremental propagation
There is also a newer and still somewhat experimental mechanism for