diff options
Diffstat (limited to 'src/config-files')
-rw-r--r-- | src/config-files/kdc.conf.M | 4 | ||||
-rw-r--r-- | src/config-files/krb5.conf.M | 10 |
2 files changed, 7 insertions, 7 deletions
diff --git a/src/config-files/kdc.conf.M b/src/config-files/kdc.conf.M index db7d5a6..b47c251 100644 --- a/src/config-files/kdc.conf.M +++ b/src/config-files/kdc.conf.M @@ -235,7 +235,7 @@ represents the master key's key type. .IP max_life This .B delta time string -specifes the maximum time period that a ticket may be valid for in +specifies the maximum time period that a ticket may be valid for in this realm. .IP max_renewable_life @@ -259,7 +259,7 @@ incremental propagation. The maximum value is 2500; default is 1000. .IP iprop_slave_poll This .B delta time string -specfies how often the slave KDC polls for new updates from the +specifies how often the slave KDC polls for new updates from the master. Default is "2m" (that is, two minutes). .IP supported_enctypes diff --git a/src/config-files/krb5.conf.M b/src/config-files/krb5.conf.M index dae196c..a082b84 100644 --- a/src/config-files/krb5.conf.M +++ b/src/config-files/krb5.conf.M @@ -123,7 +123,7 @@ Contains default values for database specific parameters. .IP [dbmodules] Contains database specific parameters used by the database library. -.ip [plugins] +.IP [plugins] Contains plugin module registration and filtering parameters. .PP Each of these sections will be covered in more details in the following @@ -230,7 +230,7 @@ Kerberos. Use a value of 1 on DCE 1.0.3a systems, and a value of 2 on DCE 1.1 systems. .IP dns_lookup_kdc -Indicate whether DNS SRV records shoud be used to locate the KDCs and +Indicate whether DNS SRV records should be used to locate the KDCs and other servers for a realm, if they are not listed in the information for the realm. The default is to use these records. @@ -541,7 +541,7 @@ and sent to the device /dev/tty04. Cross-realm authentication is typically organized hierarchically. This hierarchy is based on the name of the realm, which thus imposes restrictions on the choice of realm names, and on who may participate in -a cross-realm authentication. A non hierarchical orgization may be used, +a cross-realm authentication. A non hierarchical organization may be used, but requires a database to construct the authentication paths between the realms. This section defines that database. .PP @@ -623,11 +623,11 @@ would look like this: .sp In the above examples, the ordering is not important, except when the same subtag name is used more then once. The client will use this to -determing the path. (It is not important to the server, since the +determine the path. (It is not important to the server, since the transited field is not sorted.) .PP If this section is not present, or if the client or server cannot find a -client/server path, then normal hierarchical orginization is assumed. +client/server path, then normal hierarchical organization is assumed. .PP This feature is not currently supported by DCE. DCE security servers can be used with Kerberized clients and servers, but versions prior to DCE |