1 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
2 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
3 [<!ENTITY mdash "—">]>
5 - Copyright (C) 2008-2012 Internet Systems Consortium, Inc. ("ISC")
7 - Permission to use, copy, modify, and/or distribute this software for any
8 - purpose with or without fee is hereby granted, provided that the above
9 - copyright notice and this permission notice appear in all copies.
11 - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
12 - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
13 - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
14 - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
15 - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
16 - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
17 - PERFORMANCE OF THIS SOFTWARE.
20 <!-- $Id: dnssec-keyfromlabel.docbook,v 1.18.14.2 2011/02/28 01:19:58 tbox Exp $ -->
21 <refentry id="man.dnssec-keyfromlabel">
23 <date>February 8, 2008</date>
27 <refentrytitle><application>dnssec-keyfromlabel</application></refentrytitle>
28 <manvolnum>8</manvolnum>
29 <refmiscinfo>BIND9</refmiscinfo>
33 <refname><application>dnssec-keyfromlabel</application></refname>
34 <refpurpose>DNSSEC key generation tool</refpurpose>
44 <holder>Internet Systems Consortium, Inc. ("ISC")</holder>
50 <command>dnssec-keyfromlabel</command>
51 <arg choice="req">-l <replaceable class="parameter">label</replaceable></arg>
52 <arg><option>-3</option></arg>
53 <arg><option>-a <replaceable class="parameter">algorithm</replaceable></option></arg>
54 <arg><option>-A <replaceable class="parameter">date/offset</replaceable></option></arg>
55 <arg><option>-c <replaceable class="parameter">class</replaceable></option></arg>
56 <arg><option>-D <replaceable class="parameter">date/offset</replaceable></option></arg>
57 <arg><option>-E <replaceable class="parameter">engine</replaceable></option></arg>
58 <arg><option>-f <replaceable class="parameter">flag</replaceable></option></arg>
59 <arg><option>-G</option></arg>
60 <arg><option>-I <replaceable class="parameter">date/offset</replaceable></option></arg>
61 <arg><option>-k</option></arg>
62 <arg><option>-K <replaceable class="parameter">directory</replaceable></option></arg>
63 <arg><option>-n <replaceable class="parameter">nametype</replaceable></option></arg>
64 <arg><option>-P <replaceable class="parameter">date/offset</replaceable></option></arg>
65 <arg><option>-p <replaceable class="parameter">protocol</replaceable></option></arg>
66 <arg><option>-R <replaceable class="parameter">date/offset</replaceable></option></arg>
67 <arg><option>-t <replaceable class="parameter">type</replaceable></option></arg>
68 <arg><option>-v <replaceable class="parameter">level</replaceable></option></arg>
69 <arg><option>-y</option></arg>
70 <arg choice="req">name</arg>
75 <title>DESCRIPTION</title>
76 <para><command>dnssec-keyfromlabel</command>
77 gets keys with the given label from a crypto hardware and builds
78 key files for DNSSEC (Secure DNS), as defined in RFC 2535
82 The <option>name</option> of the key is specified on the command
83 line. This must match the name of the zone for which the key is
89 <title>OPTIONS</title>
93 <term>-a <replaceable class="parameter">algorithm</replaceable></term>
96 Selects the cryptographic algorithm. The value of
97 <option>algorithm</option> must be one of RSAMD5, RSASHA1,
98 DSA, NSEC3RSASHA1, NSEC3DSA, RSASHA256, RSASHA512, ECCGOST,
99 ECDSAP256SHA256 or ECDSAP384SHA384.
100 These values are case insensitive.
103 If no algorithm is specified, then RSASHA1 will be used by
104 default, unless the <option>-3</option> option is specified,
105 in which case NSEC3RSASHA1 will be used instead. (If
106 <option>-3</option> is used and an algorithm is specified,
107 that algorithm will be checked for compatibility with NSEC3.)
110 Note 1: that for DNSSEC, RSASHA1 is a mandatory to implement
111 algorithm, and DSA is recommended.
114 Note 2: DH automatically sets the -k flag.
123 Use an NSEC3-capable algorithm to generate a DNSSEC key.
124 If this option is used and no algorithm is explicitly
125 set on the command line, NSEC3RSASHA1 will be used by
132 <term>-E <replaceable class="parameter">engine</replaceable></term>
135 Specifies the name of the crypto hardware (OpenSSL engine).
136 When compiled with PKCS#11 support it defaults to "pkcs11".
142 <term>-l <replaceable class="parameter">label</replaceable></term>
145 Specifies the label of the key pair in the crypto hardware.
146 The label may be preceded by an optional OpenSSL engine name,
147 separated by a colon, as in "pkcs11:keylabel".
153 <term>-n <replaceable class="parameter">nametype</replaceable></term>
156 Specifies the owner type of the key. The value of
157 <option>nametype</option> must either be ZONE (for a DNSSEC
158 zone key (KEY/DNSKEY)), HOST or ENTITY (for a key associated with
160 USER (for a key associated with a user(KEY)) or OTHER (DNSKEY).
161 These values are case insensitive.
170 Compatibility mode: generates an old-style key, without
171 any metadata. By default, <command>dnssec-keyfromlabel</command>
172 will include the key's creation date in the metadata stored
173 with the private key, and other dates may be set there as well
174 (publication date, activation date, etc). Keys that include
175 this data may be incompatible with older versions of BIND; the
176 <option>-C</option> option suppresses them.
182 <term>-c <replaceable class="parameter">class</replaceable></term>
185 Indicates that the DNS record containing the key should have
186 the specified class. If not specified, class IN is used.
192 <term>-f <replaceable class="parameter">flag</replaceable></term>
195 Set the specified flag in the flag field of the KEY/DNSKEY record.
196 The only recognized flags are KSK (Key Signing Key) and REVOKE.
205 Generate a key, but do not publish it or sign with it. This
206 option is incompatible with -P and -A.
215 Prints a short summary of the options and arguments to
216 <command>dnssec-keyfromlabel</command>.
222 <term>-K <replaceable class="parameter">directory</replaceable></term>
225 Sets the directory in which the key files are to be written.
234 Generate KEY records rather than DNSKEY records.
240 <term>-p <replaceable class="parameter">protocol</replaceable></term>
243 Sets the protocol value for the key. The protocol
244 is a number between 0 and 255. The default is 3 (DNSSEC).
245 Other possible values for this argument are listed in
246 RFC 2535 and its successors.
252 <term>-t <replaceable class="parameter">type</replaceable></term>
255 Indicates the use of the key. <option>type</option> must be
256 one of AUTHCONF, NOAUTHCONF, NOAUTH, or NOCONF. The default
257 is AUTHCONF. AUTH refers to the ability to authenticate
258 data, and CONF the ability to encrypt data.
264 <term>-v <replaceable class="parameter">level</replaceable></term>
267 Sets the debugging level.
276 Allows DNSSEC key files to be generated even if the key ID
277 would collide with that of an existing key, in the event of
278 either key being revoked. (This is only safe to use if you
279 are sure you won't be using RFC 5011 trust anchor maintenance
280 with either of the keys involved.)
289 <title>TIMING OPTIONS</title>
292 Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS.
293 If the argument begins with a '+' or '-', it is interpreted as
294 an offset from the present time. For convenience, if such an offset
295 is followed by one of the suffixes 'y', 'mo', 'w', 'd', 'h', or 'mi',
296 then the offset is computed in years (defined as 365 24-hour days,
297 ignoring leap years), months (defined as 30 24-hour days), weeks,
298 days, hours, or minutes, respectively. Without a suffix, the offset
299 is computed in seconds.
304 <term>-P <replaceable class="parameter">date/offset</replaceable></term>
307 Sets the date on which a key is to be published to the zone.
308 After that date, the key will be included in the zone but will
309 not be used to sign it. If not set, and if the -G option has
310 not been used, the default is "now".
316 <term>-A <replaceable class="parameter">date/offset</replaceable></term>
319 Sets the date on which the key is to be activated. After that
320 date, the key will be included in the zone and used to sign
321 it. If not set, and if the -G option has not been used, the
328 <term>-R <replaceable class="parameter">date/offset</replaceable></term>
331 Sets the date on which the key is to be revoked. After that
332 date, the key will be flagged as revoked. It will be included
333 in the zone and will be used to sign it.
339 <term>-I <replaceable class="parameter">date/offset</replaceable></term>
342 Sets the date on which the key is to be retired. After that
343 date, the key will still be included in the zone, but it
344 will not be used to sign it.
350 <term>-D <replaceable class="parameter">date/offset</replaceable></term>
353 Sets the date on which the key is to be deleted. After that
354 date, the key will no longer be included in the zone. (It
355 may remain in the key repository, however.)
363 <title>GENERATED KEY FILES</title>
365 When <command>dnssec-keyfromlabel</command> completes
367 it prints a string of the form <filename>Knnnn.+aaa+iiiii</filename>
368 to the standard output. This is an identification string for
369 the key files it has generated.
373 <para><filename>nnnn</filename> is the key name.
377 <para><filename>aaa</filename> is the numeric representation
382 <para><filename>iiiii</filename> is the key identifier (or
387 <para><command>dnssec-keyfromlabel</command>
388 creates two files, with names based
389 on the printed string. <filename>Knnnn.+aaa+iiiii.key</filename>
390 contains the public key, and
391 <filename>Knnnn.+aaa+iiiii.private</filename> contains the
395 The <filename>.key</filename> file contains a DNS KEY record
397 can be inserted into a zone file (directly or with a $INCLUDE
401 The <filename>.private</filename> file contains
403 fields. For obvious security reasons, this file does not have
404 general read permission.
409 <title>SEE ALSO</title>
411 <refentrytitle>dnssec-keygen</refentrytitle><manvolnum>8</manvolnum>
414 <refentrytitle>dnssec-signzone</refentrytitle><manvolnum>8</manvolnum>
416 <citetitle>BIND 9 Administrator Reference Manual</citetitle>,
417 <citetitle>RFC 4034</citetitle>.
422 <title>AUTHOR</title>
423 <para><corpauthor>Internet Systems Consortium</corpauthor>