200N/A - Copyright (C) 2004-2015 Internet Systems Consortium, Inc. ("ISC") 200N/A - Copyright (C) 2000-2003 Internet Software Consortium. 200N/A - Permission to use, copy, modify, and/or distribute this software for any 200N/A - purpose with or without fee is hereby granted, provided that the above 200N/A - copyright notice and this permission notice appear in all copies. 200N/A - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH 200N/A - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY 200N/A - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT, 200N/A - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM 200N/A - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE 200N/A - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR 200N/A - PERFORMANCE OF THIS SOFTWARE. 200N/A<
meta http-
equiv="Content-Type" content="text/html; charset=ISO-8859-1">
200N/A<
title>dnssec-keyfromlabel</
title>
200N/A<
meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
1625N/A<
link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
814N/A<
body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
200N/A<
table width="100%" summary="Navigation header">
903N/A<
tr><
th colspan="3" align="center"><
span class="application">dnssec-keyfromlabel</
span></
th></
tr>
200N/A<
td width="20%" align="left">
844N/A<
th width="60%" align="center">Manual pages</
th>
200N/A<
div class="refentry" lang="en">
200N/A<
div class="refnamediv">
200N/A<
p><
span class="application">dnssec-keyfromlabel</
span> — DNSSEC key generation tool</
p>
1625N/A<
div class="refsynopsisdiv">
1625N/A<
div class="cmdsynopsis"><
p><
code class="command">dnssec-keyfromlabel</
code> {-l <
em class="replaceable"><
code>label</
code></
em>} [<
code class="option">-3</
code>] [<
code class="option">-a <
em class="replaceable"><
code>algorithm</
code></
em></
code>] [<
code class="option">-A <
em class="replaceable"><
code>
date/
offset</
code></
em></
code>] [<
code class="option">-c <
em class="replaceable"><
code>class</
code></
em></
code>] [<
code class="option">-D <
em class="replaceable"><
code>
date/
offset</
code></
em></
code>] [<
code class="option">-E <
em class="replaceable"><
code>engine</
code></
em></
code>] [<
code class="option">-f <
em class="replaceable"><
code>flag</
code></
em></
code>] [<
code class="option">-G</
code>] [<
code class="option">-I <
em class="replaceable"><
code>
date/
offset</
code></
em></
code>] [<
code class="option">-i <
em class="replaceable"><
code>interval</
code></
em></
code>] [<
code class="option">-k</
code>] [<
code class="option">-K <
em class="replaceable"><
code>directory</
code></
em></
code>] [<
code class="option">-L <
em class="replaceable"><
code>ttl</
code></
em></
code>] [<
code class="option">-n <
em class="replaceable"><
code>nametype</
code></
em></
code>] [<
code class="option">-P <
em class="replaceable"><
code>
date/
offset</
code></
em></
code>] [<
code class="option">-p <
em class="replaceable"><
code>protocol</
code></
em></
code>] [<
code class="option">-R <
em class="replaceable"><
code>
date/
offset</
code></
em></
code>] [<
code class="option">-S <
em class="replaceable"><
code>key</
code></
em></
code>] [<
code class="option">-t <
em class="replaceable"><
code>type</
code></
em></
code>] [<
code class="option">-v <
em class="replaceable"><
code>level</
code></
em></
code>] [<
code class="option">-V</
code>] [<
code class="option">-y</
code>] {name}</
p></
div>
1625N/A<
div class="refsect1" lang="en">
200N/A<
a name="id2622956"></
a><
h2>DESCRIPTION</
h2>
206N/A<
p><
span><
strong class="command">dnssec-keyfromlabel</
strong></
span>
206N/A generates a key pair of files that referencing a key object stored
206N/A in a cryptographic hardware service module (HSM). The private key
206N/A file can be used for DNSSEC signing of zone data as if it were a
200N/A conventional signing key created by <
span><
strong class="command">dnssec-keygen</
strong></
span>,
206N/A but the key material is stored within the HSM, and the actual signing
206N/A The <
code class="option">name</
code> of the key is specified on the command
200N/A line. This must match the name of the zone for which the key is
206N/A<
div class="refsect1" lang="en">
1625N/A<
a name="id2622982"></
a><
h2>OPTIONS</
h2>
1625N/A<
div class="variablelist"><
dl>
1625N/A<
dt><
span class="term">-a <
em class="replaceable"><
code>algorithm</
code></
em></
span></
dt>
1625N/A Selects the cryptographic algorithm. The value of
1625N/A <
code class="option">algorithm</
code> must be one of RSAMD5, RSASHA1,
1625N/A DSA, NSEC3RSASHA1, NSEC3DSA, RSASHA256, RSASHA512, ECCGOST,
1625N/A ECDSAP256SHA256 or ECDSAP384SHA384.
200N/A These values are case insensitive.
200N/A If no algorithm is specified, then RSASHA1 will be used by
1625N/A default, unless the <
code class="option">-3</
code> option is specified,
200N/A in which case NSEC3RSASHA1 will be used instead. (If
200N/A <
code class="option">-3</
code> is used and an algorithm is specified,
200N/A that algorithm will be checked for compatibility with NSEC3.)
200N/A Note 1: that for DNSSEC, RSASHA1 is a mandatory to implement
200N/A algorithm, and DSA is recommended.
206N/A Note 2: DH automatically sets the -k flag.
206N/A<
dt><
span class="term">-3</
span></
dt>
200N/A Use an NSEC3-capable algorithm to generate a DNSSEC key.
1625N/A If this option is used and no algorithm is explicitly
200N/A set on the command line, NSEC3RSASHA1 will be used by
1625N/A<
dt><
span class="term">-E <
em class="replaceable"><
code>engine</
code></
em></
span></
dt>
1625N/A Specifies the cryptographic hardware to use.
1625N/A When BIND is built with OpenSSL PKCS#11 support, this defaults
1625N/A to the string "pkcs11", which identifies an OpenSSL engine
1625N/A that can drive a cryptographic accelerator or hardware service
1625N/A module. When BIND is built with native PKCS#11 cryptography
1625N/A (--enable-native-pkcs11), it defaults to the path of the PKCS#11
200N/A provider library specified via "--with-pkcs11".
200N/A<
dt><
span class="term">-l <
em class="replaceable"><
code>label</
code></
em></
span></
dt>
1625N/A Specifies the label for a key pair in the crypto hardware.
200N/A When <
acronym class="acronym">BIND</
acronym> 9 is built with OpenSSL-based
200N/A PKCS#11 support, the label is an arbitrary string that
200N/A identifies a particular key. It may be preceded by an
200N/A optional OpenSSL engine name, followed by a colon, as in
206N/A "pkcs11:<
em class="replaceable"><
code>keylabel</
code></
em>".
200N/A When <
acronym class="acronym">BIND</
acronym> 9 is built with native PKCS#11
206N/A support, the label is a PKCS#11 URI string in the format
206N/A "pkcs11:<
code class="option">keyword</
code>=<
em class="replaceable"><
code>value</
code></
em>[<
span class="optional">;<
code class="option">keyword</
code>=<
em class="replaceable"><
code>value</
code></
em>;...</
span>]"
200N/A Keywords include "token", which identifies the HSM; "object", which
200N/A identifies the key; and "pin-source", which identifies a file from
200N/A which the HSM's PIN code can be obtained. The label will be
200N/A stored in the on-disk "private" file.
1625N/A <
code class="option">pin-source</
code> field, tools using the generated
200N/A key files will be able to use the HSM for signing and other
1625N/A operations without any need for an operator to manually enter
1625N/A a PIN. Note: Making the HSM's PIN accessible in this manner
1625N/A may reduce the security advantage of using an HSM; be sure
1625N/A this is what you want to do before making use of this feature.
1625N/A<
dt><
span class="term">-n <
em class="replaceable"><
code>nametype</
code></
em></
span></
dt>
1625N/A Specifies the owner type of the key. The value of
1625N/A <
code class="option">nametype</
code> must either be ZONE (for a DNSSEC
1625N/A USER (for a key associated with a user(KEY)) or OTHER (DNSKEY).
1625N/A These values are case insensitive.
1625N/A<
dt><
span class="term">-C</
span></
dt>
1625N/A Compatibility mode: generates an old-style key, without
1625N/A any metadata. By default, <
span><
strong class="command">dnssec-keyfromlabel</
strong></
span>
1625N/A will include the key's creation date in the metadata stored
1625N/A with the private key, and other dates may be set there as well
1625N/A (publication date, activation date, etc). Keys that include
200N/A this data may be incompatible with older versions of BIND; the
200N/A <
code class="option">-C</
code> option suppresses them.
200N/A<
dt><
span class="term">-c <
em class="replaceable"><
code>class</
code></
em></
span></
dt>
Indicates that the DNS record containing the key should have
the specified class. If not specified, class IN is used.
<
dt><
span class="term">-f <
em class="replaceable"><
code>flag</
code></
em></
span></
dt>
Set the specified flag in the flag field of the
KEY/
DNSKEY record.
The only recognized flags are KSK (Key Signing Key) and REVOKE.
<
dt><
span class="term">-G</
span></
dt>
Generate a key, but do not publish it or sign with it. This
option is incompatible with -P and -A.
<
dt><
span class="term">-h</
span></
dt>
Prints a short summary of the options and arguments to
<
span><
strong class="command">dnssec-keyfromlabel</
strong></
span>.
<
dt><
span class="term">-K <
em class="replaceable"><
code>directory</
code></
em></
span></
dt>
Sets the directory in which the key files are to be written.
<
dt><
span class="term">-k</
span></
dt>
Generate KEY records rather than DNSKEY records.
<
dt><
span class="term">-L <
em class="replaceable"><
code>ttl</
code></
em></
span></
dt>
Sets the default TTL to use for this key when it is converted
into a DNSKEY RR. If the key is imported into a zone,
this is the TTL that will be used for it, unless there was
already a DNSKEY RRset in place, in which case the existing TTL
would take precedence. Setting the default TTL to
<
code class="literal">0</
code> or <
code class="literal">none</
code> removes it.
<
dt><
span class="term">-p <
em class="replaceable"><
code>protocol</
code></
em></
span></
dt>
Sets the protocol value for the 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.
<
dt><
span class="term">-S <
em class="replaceable"><
code>key</
code></
em></
span></
dt>
Generate a key as an explicit successor to an existing key.
The name, algorithm, size, and type of the key will be set
to match the predecessor. The activation date of the new
key will be set to the inactivation date of the existing
one. The publication date will be set to the activation
date minus the prepublication interval, which defaults to
<
dt><
span class="term">-t <
em class="replaceable"><
code>type</
code></
em></
span></
dt>
Indicates the use of the key. <
code class="option">type</
code> 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.
<
dt><
span class="term">-v <
em class="replaceable"><
code>level</
code></
em></
span></
dt>
Sets the debugging level.
<
dt><
span class="term">-V</
span></
dt>
Prints version information.
<
dt><
span class="term">-y</
span></
dt>
Allows DNSSEC key files to be generated even if the key ID
would collide with that of an existing key, in the event of
either key being revoked. (This is only safe to use if you
are sure you won't be using RFC 5011 trust anchor maintenance
with either of the keys involved.)
<
div class="refsect1" lang="en">
<
a name="id2677313"></
a><
h2>TIMING OPTIONS</
h2>
Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS.
If the argument begins with a '+' or '-', it is interpreted as
an offset from the present time. For convenience, if such an offset
is followed by one of the suffixes 'y', 'mo', 'w', 'd', 'h', or 'mi',
then the offset is computed in years (defined as 365 24-hour days,
ignoring leap years), months (defined as 30 24-hour days), weeks,
days, hours, or minutes, respectively. Without a suffix, the offset
is computed in seconds. To explicitly prevent a date from being
set, use 'none' or 'never'.
<
div class="variablelist"><
dl>
<
dt><
span class="term">-P <
em class="replaceable"><
code>
date/
offset</
code></
em></
span></
dt>
Sets the date on which a key is to be published to the zone.
After that date, the key will be included in the zone but will
not be used to sign it. If not set, and if the -G option has
not been used, the default is "now".
<
dt><
span class="term">-A <
em class="replaceable"><
code>
date/
offset</
code></
em></
span></
dt>
Sets the date on which the key is to be activated. After that
date, the key will be included in the zone and used to sign
it. If not set, and if the -G option has not been used, the
<
dt><
span class="term">-R <
em class="replaceable"><
code>
date/
offset</
code></
em></
span></
dt>
Sets the date on which the key is to be revoked. After that
date, the key will be flagged as revoked. It will be included
in the zone and will be used to sign it.
<
dt><
span class="term">-I <
em class="replaceable"><
code>
date/
offset</
code></
em></
span></
dt>
Sets the date on which the key is to be retired. After that
date, the key will still be included in the zone, but it
will not be used to sign it.
<
dt><
span class="term">-D <
em class="replaceable"><
code>
date/
offset</
code></
em></
span></
dt>
Sets the date on which the key is to be deleted. After that
date, the key will no longer be included in the zone. (It
may remain in the key repository, however.)
<
dt><
span class="term">-i <
em class="replaceable"><
code>interval</
code></
em></
span></
dt>
Sets the prepublication interval for a key. If set, then
the publication and activation dates must be separated by at least
this much time. If the activation date is specified but the
publication date isn't, then the publication date will default
to this much time before the activation date; conversely, if
the publication date is specified but activation date isn't,
then activation will be set to this much time after publication.
If the key is being created as an explicit successor to another
key, then the default prepublication interval is 30 days;
As with date offsets, if the argument is followed by one of
the suffixes 'y', 'mo', 'w', 'd', 'h', or 'mi', then the
interval is measured in years, months, weeks, days, hours,
or minutes, respectively. Without a suffix, the interval is
<
div class="refsect1" lang="en">
<
a name="id2677502"></
a><
h2>GENERATED KEY FILES</
h2>
When <
span><
strong class="command">dnssec-keyfromlabel</
strong></
span> completes
it prints a string of the form <
code class="filename">Knnnn.+aaa+iiiii</
code>
to the standard output. This is an identification string for
the key files it has generated.
<
div class="itemizedlist"><
ul type="disc">
<
li><
p><
code class="filename">nnnn</
code> is the key name.
<
li><
p><
code class="filename">aaa</
code> is the numeric representation
<
li><
p><
code class="filename">iiiii</
code> is the key identifier (or
<
p><
span><
strong class="command">dnssec-keyfromlabel</
strong></
span>
creates two files, with names based
on the printed string. <
code class="filename">Knnnn.+aaa+
iiiii.key</
code>
contains the public key, and
<
code class="filename">Knnnn.+aaa+
iiiii.private</
code> contains the
The <
code class="filename">.key</
code> file contains a DNS KEY record
can be inserted into a zone file (directly or with a $INCLUDE
The <
code class="filename">.private</
code> file contains
fields. For obvious security reasons, this file does not have
<
div class="refsect1" lang="en">
<
a name="id2677596"></
a><
h2>SEE ALSO</
h2>
<
p><
span class="citerefentry"><
span class="refentrytitle">dnssec-keygen</
span>(8)</
span>,
<
span class="citerefentry"><
span class="refentrytitle">dnssec-signzone</
span>(8)</
span>,
<
em class="citetitle">BIND 9 Administrator Reference Manual</
em>,
<
em class="citetitle">RFC 4034</
em>,
<
em class="citetitle">The PKCS#11 URI Scheme (draft-pechanec-pkcs11uri-13)</
em>.
<
div class="refsect1" lang="en">
<
a name="id2677634"></
a><
h2>AUTHOR</
h2>
<
p><
span class="corpauthor">Internet Systems Consortium</
span>
<
table width="100%" summary="Navigation footer">
<
td width="40%" align="left">
<
td width="20%" align="center"><
a accesskey="u" href="Bv9ARM.ch13.html">Up</
a></
td>
<
td width="40%" align="left" valign="top">
<
span class="application">dnssec-importkey</
span>�</
td>
<
td width="20%" align="center"><
a accesskey="h" href="Bv9ARM.html">Home</
a></
td>
<
td width="40%" align="right" valign="top">�<
span class="application">dnssec-keygen</
span>
<
p style="text-align: center;">BIND 9.11.0pre-alpha</
p>