]> git.ipfire.org Git - thirdparty/bind9.git/commitdiff
cleanup dnssec-keygen manual page
authorTony Finch <dot@dotat.at>
Thu, 21 Feb 2019 18:54:16 +0000 (18:54 +0000)
committerEvan Hunt <each@isc.org>
Thu, 7 Mar 2019 01:34:26 +0000 (17:34 -0800)
Alphabetize options and synopsis; remove spurious -z from synopsis;
refer to -T KEY in options that are only relevant to pre-RFC3755
DNSSEC, and add a -f KSK example.

(cherry picked from commit 1954f8d2bf92ab19efa20eed12ba986ae2988222)

CHANGES
bin/dnssec/dnssec-keygen.docbook

diff --git a/CHANGES b/CHANGES
index 99c9da3704de3b45ac10e89178f0db03b820dce6..4da678feb74b7ec573d8e1cb108247658d8ef59d 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -1,6 +1,8 @@
 5176.  [tests]         Remove a dependency on libxml in statschannel system
                        test. [GL #926]
 
+5174.  [doc]           Tidy dnssec-keygen manual. [GL !1557]
+
 5172.  [bug]           nsupdate now honors the operating system's preferred
                        ephemeral port range. [GL #905]
 
index ee6a48936caa53567b41e0cd142fc4a1c96252bf..0ae6b41ac6118427c994b8b3491fab42c4ca9b20 100644 (file)
   <refsynopsisdiv>
     <cmdsynopsis sepchar=" ">
       <command>dnssec-keygen</command>
-      <arg choice="opt" rep="norepeat"><option>-a <replaceable class="parameter">algorithm</replaceable></option></arg>
-      <arg choice="opt" rep="norepeat"><option>-b <replaceable class="parameter">keysize</replaceable></option></arg>
-      <arg choice="opt" rep="norepeat"><option>-n <replaceable class="parameter">nametype</replaceable></option></arg>
       <arg choice="opt" rep="norepeat"><option>-3</option></arg>
       <arg choice="opt" rep="norepeat"><option>-A <replaceable class="parameter">date/offset</replaceable></option></arg>
+      <arg rep="norepeat"><option>-a <replaceable class="parameter">algorithm</replaceable></option></arg>
+      <arg choice="opt" rep="norepeat"><option>-b <replaceable class="parameter">keysize</replaceable></option></arg>
       <arg choice="opt" rep="norepeat"><option>-C</option></arg>
       <arg choice="opt" rep="norepeat"><option>-c <replaceable class="parameter">class</replaceable></option></arg>
       <arg choice="opt" rep="norepeat"><option>-D <replaceable class="parameter">date/offset</replaceable></option></arg>
@@ -77,6 +76,7 @@
       <arg choice="opt" rep="norepeat"><option>-K <replaceable class="parameter">directory</replaceable></option></arg>
       <arg choice="opt" rep="norepeat"><option>-k</option></arg>
       <arg choice="opt" rep="norepeat"><option>-L <replaceable class="parameter">ttl</replaceable></option></arg>
+      <arg choice="opt" rep="norepeat"><option>-n <replaceable class="parameter">nametype</replaceable></option></arg>
       <arg choice="opt" rep="norepeat"><option>-P <replaceable class="parameter">date/offset</replaceable></option></arg>
       <arg choice="opt" rep="norepeat"><option>-P sync <replaceable class="parameter">date/offset</replaceable></option></arg>
       <arg choice="opt" rep="norepeat"><option>-p <replaceable class="parameter">protocol</replaceable></option></arg>
@@ -88,7 +88,6 @@
       <arg choice="opt" rep="norepeat"><option>-t <replaceable class="parameter">type</replaceable></option></arg>
       <arg choice="opt" rep="norepeat"><option>-V</option></arg>
       <arg choice="opt" rep="norepeat"><option>-v <replaceable class="parameter">level</replaceable></option></arg>
-      <arg choice="opt" rep="norepeat"><option>-z</option></arg>
       <arg choice="req" rep="norepeat">name</arg>
     </cmdsynopsis>
   </refsynopsisdiv>
 
 
     <variablelist>
+
+      <varlistentry>
+       <term>-3</term>
+       <listitem>
+         <para>
+           Use an NSEC3-capable algorithm to generate a DNSSEC key.
+           If this option is used with an algorithm that has both
+           NSEC and NSEC3 versions, then the NSEC3 version will be
+           used; for example, <command>dnssec-keygen -3a RSASHA1</command>
+           specifies the NSEC3RSASHA1 algorithm.
+         </para>
+       </listitem>
+      </varlistentry>
+
       <varlistentry>
        <term>-a <replaceable class="parameter">algorithm</replaceable></term>
        <listitem>
        </listitem>
       </varlistentry>
 
-      <varlistentry>
-       <term>-n <replaceable class="parameter">nametype</replaceable></term>
-       <listitem>
-         <para>
-           Specifies the owner type of the key.  The value of
-           <option>nametype</option> must either be ZONE (for a DNSSEC
-           zone key (KEY/DNSKEY)), HOST or ENTITY (for a key associated with
-           a host (KEY)),
-           USER (for a key associated with a user(KEY)) or OTHER (DNSKEY).
-           These values are case insensitive.  Defaults to ZONE for DNSKEY
-           generation.
-         </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term>-3</term>
-       <listitem>
-         <para>
-           Use an NSEC3-capable algorithm to generate a DNSSEC key.
-           If this option is used and no algorithm is explicitly
-           set on the command line, NSEC3RSASHA1 will be used by
-           default. Note that RSASHA256, RSASHA512, ECCGOST,
-           ECDSAP256SHA256, ECDSAP384SHA384, ED25519 and ED448
-           algorithms are NSEC3-capable.
-         </para>
-       </listitem>
-      </varlistentry>
-
       <varlistentry>
        <term>-C</term>
        <listitem>
          <para>
-           Compatibility mode:  generates an old-style key, without
-           any metadata.  By default, <command>dnssec-keygen</command>
-           will include the key's creation date in the metadata stored
-           with the private key, and other dates may be set there as well
-           (publication date, activation date, etc).  Keys that include
-           this data may be incompatible with older versions of BIND; the
+           Compatibility mode: generates an old-style key, without any
+           timing metadata. By default, <command>dnssec-keygen</command>
+           will include the key's creation date in the metadata stored with
+           the private key, and other dates may be set there as well
+           (publication date, activation date, etc). Keys that include this
+           data may be incompatible with older versions of BIND; the
            <option>-C</option> option suppresses them.
          </para>
        </listitem>
        </listitem>
       </varlistentry>
 
+      <varlistentry>
+       <term>-n <replaceable class="parameter">nametype</replaceable></term>
+       <listitem>
+         <para>
+           Specifies the owner type of the key.  The value of
+           <option>nametype</option> must either be ZONE (for a DNSSEC
+           zone key (KEY/DNSKEY)), HOST or ENTITY (for a key associated
+           with a host (KEY)), USER (for a key associated with a
+           user(KEY)) or OTHER (DNSKEY).  These values are case
+           insensitive.  Defaults to ZONE for DNSKEY generation.
+         </para>
+       </listitem>
+      </varlistentry>
+
       <varlistentry>
        <term>-p <replaceable class="parameter">protocol</replaceable></term>
        <listitem>
          <para>
-           Sets the protocol value for the generated key.  The protocol
-           is a number between 0 and 255.  The default is 3 (DNSSEC).
-           Other possible values for this argument are listed in
-           RFC 2535 and its successors.
+           Sets the protocol value for the generated key, for use
+           with <option>-T KEY</option>. The protocol is a number between 0
+           and 255. The default is 3 (DNSSEC). Other possible values for
+           this argument are listed in RFC 2535 and its successors.
          </para>
        </listitem>
       </varlistentry>
        <term>-t <replaceable class="parameter">type</replaceable></term>
        <listitem>
          <para>
-           Indicates the use of the key.  <option>type</option> must be
-           one of AUTHCONF, NOAUTHCONF, NOAUTH, or NOCONF.  The default
-           is AUTHCONF.  AUTH refers to the ability to authenticate
-           data, and CONF the ability to encrypt data.
+           Indicates the use of the key, for use with <option>-T
+           KEY</option>. <option>type</option> must be one of AUTHCONF,
+           NOAUTHCONF, NOAUTH, or NOCONF. The default is AUTHCONF. AUTH
+           refers to the ability to authenticate data, and CONF the ability
+           to encrypt data.
          </para>
        </listitem>
       </varlistentry>
 
       <varlistentry>
-       <term>-v <replaceable class="parameter">level</replaceable></term>
+       <term>-V</term>
        <listitem>
          <para>
-           Sets the debugging level.
+           Prints version information.
          </para>
        </listitem>
       </varlistentry>
 
       <varlistentry>
-       <term>-V</term>
+       <term>-v <replaceable class="parameter">level</replaceable></term>
        <listitem>
          <para>
-           Prints version information.
+           Sets the debugging level.
          </para>
        </listitem>
       </varlistentry>
       and
       <filename>Kexample.com.+003+26160.private</filename>.
     </para>
+    <para>
+      To generate a matching key-signing key, issue the command:
+    </para>
+    <para>
+      <userinput>dnssec-keygen -a DSA -b 768 -n ZONE -f KSK example.com</userinput>
+    </para>
   </refsection>
 
   <refsection><info><title>SEE ALSO</title></info>