Document "first introduced version" in conf files

For the config options that were introduced starting from release 1.9,
specify the release number.

diff --git a/doc/admin/conf_files/kdc_conf.rst b/doc/admin/conf_files/kdc_conf.rst
index 7631431051eebd1f0e5845f91ead4baf289ba0ef..c10e81e7e1bdb7c95137eb673527822d758fd00a 100644 (file)
--- a/doc/admin/conf_files/kdc_conf.rst
+++ b/doc/admin/conf_files/kdc_conf.rst
@@ -210,7 +210,7 @@ For each realm, the following tags may be specified:
     (Delta time string.)  Specifies the amount of time to wait for a
     full propagation to complete.  This is optional in configuration
     files, and is used by slave KDCs only.  The default value is 5
-    minutes (``5m``).
+    minutes (``5m``).  First introduced in release 1.11.
 
 **iprop_logfile**
     (File name.)  Specifies where the update log file for the realm
@@ -283,6 +283,7 @@ For each realm, the following tags may be specified:
     purposes.  If **allow_weak_crypto** in :ref:`libdefaults` is
     false, or if des-cbc-crc is not a permitted enctype, then this
     variable has no effect.  Defaults to true.
+    First introduced in release 1.11.
 
 **reject_bad_transit**
     (Boolean value.)  If set to true, the KDC will check the list of
@@ -311,7 +312,7 @@ For each realm, the following tags may be specified:
     than the realm's ticket-granting service.  This option allows
     anonymous PKINIT to be enabled for use as FAST armor tickets
     without allowing anonymous authentication to services.  The
-    default value is false.
+    default value is false.  First introduced in release 1.9.
 
 **supported_enctypes**
     (List of *key*:*salt* strings.)  Specifies the default key/salt
@@ -373,14 +374,14 @@ the subsection:
     preauthentication.  Setting this flag may improve performance.
     (Principal entries which do not require preauthentication never
     update the "Last successful authentication" field.).  First
-    introduced in version 1.9.
+    introduced in release 1.9.
 
 **disable_lockout**
     If set to ``true``, suppresses KDC updates to the "Last failed
     authentication" and "Failed password attempts" fields of principal
     entries requiring preauthentication.  Setting this flag may
     improve performance, but also disables account lockout.  First
-    introduced in version 1.9.
+    introduced in release 1.9.
 
 **ldap_conns_per_server**
     This LDAP-specific tag indicates the number of connections to be

diff --git a/doc/admin/conf_files/krb5_conf.rst b/doc/admin/conf_files/krb5_conf.rst
index 60a9d06ff23d3455a6e90f2e82aa4b9239dbc37d..4c8f75654188a3ae58596e91a260e82e587dbce7 100644 (file)
--- a/doc/admin/conf_files/krb5_conf.rst
+++ b/doc/admin/conf_files/krb5_conf.rst
@@ -137,12 +137,13 @@ The libdefaults section may contain any of the following relations:
 **default_ccache_name**
     This relation specifies the name of the default credential cache.
     The default is |ccache|.  This relation is subject to parameter
-    expansion (see below).
+    expansion (see below).  First introduced in release 1.11.
 
 **default_client_keytab_name**
     This relation specifies the name of the default keytab for
     obtaining client credentials.  The default is |ckeytab|.  This
     relation is subject to parameter expansion (see below).
+    First introduced in release 1.11.
 
 **default_keytab_name**
     This relation specifies the default keytab name to be used by
@@ -219,7 +220,7 @@ The libdefaults section may contain any of the following relations:
     (if given).  This option can improve the administrative
     flexibility of server applications on multihomed hosts, but could
     compromise the security of virtual hosting environments.  The
-    default value is false.
+    default value is false.  First introduced in release 1.10.
 
 **k5login_authoritative**
     If this flag is true, principals must be listed in a local user's
@@ -635,6 +636,8 @@ modules and to turn modules on and off.  Not every krb5 pluggable
 interface uses the [plugins] section; the ones that do are documented
 here.
 
+First introduced in release 1.9.
+
 Each pluggable interface corresponds to a subsection of [plugins].
 All subsections support the same tags: