Move supported enc/salt type docs to kdc.conf(5)

[krb5.git] / doc / rst_source / krb_admins / admin_commands / kdb5_util.rst

diff --git a/doc/rst_source/krb_admins/admin_commands/kdb5_util.rst b/doc/rst_source/krb_admins/admin_commands/kdb5_util.rst
index 9184df17b9171caa960d75f58631673bba4c4222..e454a7c53d4c121e6e94430cde1c54600912c5d0 100644 (file)
--- a/doc/rst_source/krb_admins/admin_commands/kdb5_util.rst
+++ b/doc/rst_source/krb_admins/admin_commands/kdb5_util.rst
@@ -52,8 +52,9 @@ COMMAND-LINE OPTIONS
     value.
 
 **-k** *mkeytype*
-    specifies the key type of the master key in the database; the
-    default is that given in :ref:`kdc.conf(5)`.
+    specifies the key type of the master key in the database.  The
+    default is given by the **master_key_type** variable in
+    :ref:`kdc.conf(5)`.
 
 **-kv** *mkeyVNO*
     Specifies the version number of the master key in the database;
@@ -260,9 +261,10 @@ add_mkey
 
 Adds a new master key to the master key principal, but does not mark
 it as active.  Existing master keys will remain.  The **-e** option
-specifies of the encryption type of the new master key.  The **-s**
-option stashes the new master key in the stash file, which will be
-created if it doesn't already exist.
+specifies the encryption type of the new master key; see
+:ref:`Encryption_and_salt_types` in :ref:`kdc.conf(5)` for a list of
+possible values.  The **-s** option stashes the new master key in the
+stash file, which will be created if it doesn't already exist.
 
 After a new master key is added, it should be propagated to slave
 servers via a manual or periodic invocation of :ref:`kprop(8)`.  Then,