aboutsummaryrefslogtreecommitdiff
path: root/handbook/kerberos.sgml
diff options
context:
space:
mode:
authorJohn Fieber <jfieber@FreeBSD.org>1995-10-12 03:18:14 +0000
committerJohn Fieber <jfieber@FreeBSD.org>1995-10-12 03:18:14 +0000
commit4c0228d53f2f7c53cd84a06d3ff1d2575ff2cad9 (patch)
tree88e8f52c425a118ebec84390f88a80175bd89b04 /handbook/kerberos.sgml
parentf7c869a24d17ed9ebade61bbab62aef0825867d4 (diff)
downloaddoc-4c0228d53f2f7c53cd84a06d3ff1d2575ff2cad9.tar.gz
doc-4c0228d53f2f7c53cd84a06d3ff1d2575ff2cad9.zip
Sync with head.
Notes
Notes: svn path=/branches/RELENG_2_1_0/; revision=120
Diffstat (limited to 'handbook/kerberos.sgml')
-rw-r--r--handbook/kerberos.sgml8
1 files changed, 4 insertions, 4 deletions
diff --git a/handbook/kerberos.sgml b/handbook/kerberos.sgml
index 39ac95d55c..f65fa4d440 100644
--- a/handbook/kerberos.sgml
+++ b/handbook/kerberos.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: kerberos.sgml,v 1.2.4.1 1995-09-17 11:19:32 davidg Exp $ -->
+<!-- $Id: kerberos.sgml,v 1.2.4.2 1995-10-12 03:16:05 jfieber Exp $ -->
<!-- The FreeBSD Documentation Project -->
<sect><heading>Kerberos<label id="kerberos"></heading>
@@ -226,7 +226,7 @@ grunt# mv grunt-new-srvtab srvtab
<p>If the file is for a client system, and the network is not
deemed safe, then copy the <tt>&lt;client&gt;-new-srvtab</tt> to
- removeable media and transport it by secure physical means. Be
+ removable media and transport it by secure physical means. Be
sure to rename it to <tt>srvtab</tt> in the client's
<tt>/etc/kerberosIV</tt> directory, and make sure it is mode 600:
@@ -325,7 +325,7 @@ Apr 30 11:23:22 Apr 30 19:23:22 krbtgt.GRONDAR.ZA@GRONDAR.ZA
</verb></tscreen>
<p>Now try changing the password using <tt>passwd</tt> to check if the
- kpasswd daemon can get authorisation to the Kerberos database:
+ kpasswd daemon can get authorization to the Kerberos database:
<tscreen><verb>
grunt$ passwd
@@ -342,7 +342,7 @@ Password changed.
<p>Kerberos allows us to give <it>each</it> user who needs root
privileges their own <it>separate</it> <tt>su</tt>password. We
- could now add an id which is authorised to <tt>su</tt> to <it>root</it>.
+ could now add an id which is authorized to <tt>su</tt> to <it>root</it>.
This is controlled by having an instance of <it>root</it> associated
with a principal. Using <tt>kdb_edit</tt> we can create the entry
<it>jane.root</it> in the Kerberos database: