man.dnssec-keyfromlabel.html revision 299e3f18eb4f9297e6f06ca373806b07bec13a02
961N/A<!--
961N/A - Copyright (C) 2004-2013 Internet Systems Consortium, Inc. ("ISC")
961N/A - Copyright (C) 2000-2003 Internet Software Consortium.
961N/A -
961N/A - Permission to use, copy, modify, and/or distribute this software for any
961N/A - purpose with or without fee is hereby granted, provided that the above
961N/A - copyright notice and this permission notice appear in all copies.
961N/A -
961N/A - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
961N/A - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
961N/A - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
961N/A - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
961N/A - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
961N/A - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
961N/A - PERFORMANCE OF THIS SOFTWARE.
961N/A-->
961N/A<!-- $Id$ -->
961N/A<html>
961N/A<head>
961N/A<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
961N/A<title>dnssec-keyfromlabel</title>
961N/A<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
961N/A<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
961N/A<link rel="up" href="Bv9ARM.ch10.html" title="Manual pages">
5072N/A<link rel="prev" href="man.dnssec-dsfromkey.html" title="dnssec-dsfromkey">
6341N/A<link rel="next" href="man.dnssec-keygen.html" title="dnssec-keygen">
961N/A</head>
961N/A<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
961N/A<div class="navheader">
5072N/A<table width="100%" summary="Navigation header">
1298N/A<tr><th colspan="3" align="center"><span class="application">dnssec-keyfromlabel</span></th></tr>
1298N/A<tr>
1298N/A<td width="20%" align="left">
1298N/A<a accesskey="p" href="man.dnssec-dsfromkey.html">Prev</a>�</td>
1298N/A<th width="60%" align="center">Manual pages</th>
1298N/A<td width="20%" align="right">�<a accesskey="n" href="man.dnssec-keygen.html">Next</a>
1298N/A</td>
1298N/A</tr>
1298N/A</table>
1298N/A<hr>
1298N/A</div>
1298N/A<div class="refentry" lang="en">
1298N/A<a name="man.dnssec-keyfromlabel"></a><div class="titlepage"></div>
6341N/A<div class="refnamediv">
961N/A<h2>Name</h2>
961N/A<p><span class="application">dnssec-keyfromlabel</span> &#8212; DNSSEC key generation tool</p>
961N/A</div>
961N/A<div class="refsynopsisdiv">
961N/A<h2>Synopsis</h2>
961N/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">-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">-t <em class="replaceable"><code>type</code></em></code>] [<code class="option">-v <em class="replaceable"><code>level</code></em></code>] [<code class="option">-y</code>] {name}</p></div>
961N/A</div>
961N/A<div class="refsect1" lang="en">
961N/A<a name="id2618078"></a><h2>DESCRIPTION</h2>
961N/A<p><span><strong class="command">dnssec-keyfromlabel</strong></span>
961N/A gets keys with the given label from a crypto hardware and builds
961N/A key files for DNSSEC (Secure DNS), as defined in RFC 2535
961N/A and RFC 4034.
3765N/A </p>
3765N/A<p>
3765N/A The <code class="option">name</code> of the key is specified on the command
961N/A line. This must match the name of the zone for which the key is
5072N/A being generated.
5072N/A </p>
1878N/A</div>
1298N/A<div class="refsect1" lang="en">
961N/A<a name="id2618099"></a><h2>OPTIONS</h2>
961N/A<div class="variablelist"><dl>
961N/A<dt><span class="term">-a <em class="replaceable"><code>algorithm</code></em></span></dt>
961N/A<dd>
961N/A<p>
961N/A Selects the cryptographic algorithm. The value of
961N/A <code class="option">algorithm</code> must be one of RSAMD5, RSASHA1,
3765N/A DSA, NSEC3RSASHA1, NSEC3DSA, RSASHA256, RSASHA512, ECCGOST,
3765N/A ECDSAP256SHA256 or ECDSAP384SHA384.
3765N/A These values are case insensitive.
3765N/A </p>
3765N/A<p>
3765N/A If no algorithm is specified, then RSASHA1 will be used by
3765N/A default, unless the <code class="option">-3</code> option is specified,
961N/A in which case NSEC3RSASHA1 will be used instead. (If
961N/A <code class="option">-3</code> is used and an algorithm is specified,
961N/A that algorithm will be checked for compatibility with NSEC3.)
961N/A </p>
1298N/A<p>
1298N/A Note 1: that for DNSSEC, RSASHA1 is a mandatory to implement
1298N/A algorithm, and DSA is recommended.
1298N/A </p>
1298N/A<p>
1298N/A Note 2: DH automatically sets the -k flag.
1298N/A </p>
1298N/A</dd>
1298N/A<dt><span class="term">-3</span></dt>
1298N/A<dd><p>
961N/A Use an NSEC3-capable algorithm to generate a DNSSEC key.
961N/A If this option is used and no algorithm is explicitly
1298N/A set on the command line, NSEC3RSASHA1 will be used by
1298N/A default.
5072N/A </p></dd>
1298N/A<dt><span class="term">-E <em class="replaceable"><code>engine</code></em></span></dt>
1298N/A<dd><p>
1298N/A Specifies the name of the crypto hardware (OpenSSL engine).
5072N/A When compiled with PKCS#11 support it defaults to "pkcs11".
5072N/A </p></dd>
1878N/A<dt><span class="term">-l <em class="replaceable"><code>label</code></em></span></dt>
1298N/A<dd><p>
1298N/A Specifies the label of the key pair in the crypto hardware.
961N/A The label may be preceded by an optional OpenSSL engine name,
961N/A separated by a colon, as in "pkcs11:keylabel".
961N/A </p></dd>
5072N/A<dt><span class="term">-n <em class="replaceable"><code>nametype</code></em></span></dt>
5072N/A<dd><p>
5072N/A Specifies the owner type of the key. The value of
5072N/A <code class="option">nametype</code> must either be ZONE (for a DNSSEC
5072N/A zone key (KEY/DNSKEY)), HOST or ENTITY (for a key associated with
5072N/A a host (KEY)),
5072N/A USER (for a key associated with a user(KEY)) or OTHER (DNSKEY).
5072N/A These values are case insensitive.
5072N/A </p></dd>
5072N/A<dt><span class="term">-C</span></dt>
5072N/A<dd><p>
5072N/A Compatibility mode: generates an old-style key, without
5072N/A any metadata. By default, <span><strong class="command">dnssec-keyfromlabel</strong></span>
5072N/A will include the key's creation date in the metadata stored
5072N/A with the private key, and other dates may be set there as well
5072N/A (publication date, activation date, etc). Keys that include
5072N/A this data may be incompatible with older versions of BIND; the
5072N/A <code class="option">-C</code> option suppresses them.
5072N/A </p></dd>
5072N/A<dt><span class="term">-c <em class="replaceable"><code>class</code></em></span></dt>
5072N/A<dd><p>
5072N/A Indicates that the DNS record containing the key should have
5072N/A the specified class. If not specified, class IN is used.
5072N/A </p></dd>
5072N/A<dt><span class="term">-f <em class="replaceable"><code>flag</code></em></span></dt>
5072N/A<dd><p>
5072N/A Set the specified flag in the flag field of the KEY/DNSKEY record.
5072N/A The only recognized flags are KSK (Key Signing Key) and REVOKE.
5072N/A </p></dd>
5072N/A<dt><span class="term">-G</span></dt>
5072N/A<dd><p>
5072N/A Generate a key, but do not publish it or sign with it. This
5072N/A option is incompatible with -P and -A.
5072N/A </p></dd>
5072N/A<dt><span class="term">-h</span></dt>
5072N/A<dd><p>
5072N/A Prints a short summary of the options and arguments to
5072N/A <span><strong class="command">dnssec-keyfromlabel</strong></span>.
5072N/A </p></dd>
5072N/A<dt><span class="term">-K <em class="replaceable"><code>directory</code></em></span></dt>
5072N/A<dd><p>
5072N/A Sets the directory in which the key files are to be written.
5072N/A </p></dd>
5072N/A<dt><span class="term">-k</span></dt>
5072N/A<dd><p>
5072N/A Generate KEY records rather than DNSKEY records.
5072N/A </p></dd>
5072N/A<dt><span class="term">-L <em class="replaceable"><code>ttl</code></em></span></dt>
5072N/A<dd><p>
5072N/A Sets the default TTL to use for this key when it is converted
5072N/A into a DNSKEY RR. If the key is imported into a zone,
5072N/A this is the TTL that will be used for it, unless there was
5072N/A already a DNSKEY RRset in place, in which case the existing TTL
5072N/A would take precedence. Setting the default TTL to
5072N/A <code class="literal">0</code> or <code class="literal">none</code> removes it.
5072N/A </p></dd>
5072N/A<dt><span class="term">-p <em class="replaceable"><code>protocol</code></em></span></dt>
5072N/A<dd><p>
5072N/A Sets the protocol value for the key. The protocol
5072N/A is a number between 0 and 255. The default is 3 (DNSSEC).
5072N/A Other possible values for this argument are listed in
5072N/A RFC 2535 and its successors.
5072N/A </p></dd>
5072N/A<dt><span class="term">-t <em class="replaceable"><code>type</code></em></span></dt>
5072N/A<dd><p>
961N/A Indicates the use of the key. <code class="option">type</code> must be
961N/A one of AUTHCONF, NOAUTHCONF, NOAUTH, or NOCONF. The default
961N/A is AUTHCONF. AUTH refers to the ability to authenticate
961N/A data, and CONF the ability to encrypt data.
961N/A </p></dd>
5072N/A<dt><span class="term">-v <em class="replaceable"><code>level</code></em></span></dt>
961N/A<dd><p>
1298N/A Sets the debugging level.
961N/A </p></dd>
961N/A<dt><span class="term">-y</span></dt>
961N/A<dd><p>
5072N/A Allows DNSSEC key files to be generated even if the key ID
961N/A would collide with that of an existing key, in the event of
961N/A either key being revoked. (This is only safe to use if you
961N/A are sure you won't be using RFC 5011 trust anchor maintenance
961N/A with either of the keys involved.)
961N/A </p></dd>
961N/A</dl></div>
961N/A</div>
961N/A<div class="refsect1" lang="en">
1298N/A<a name="id2620338"></a><h2>TIMING OPTIONS</h2>
961N/A<p>
961N/A Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS.
961N/A If the argument begins with a '+' or '-', it is interpreted as
961N/A an offset from the present time. For convenience, if such an offset
1298N/A is followed by one of the suffixes 'y', 'mo', 'w', 'd', 'h', or 'mi',
961N/A then the offset is computed in years (defined as 365 24-hour days,
961N/A ignoring leap years), months (defined as 30 24-hour days), weeks,
961N/A days, hours, or minutes, respectively. Without a suffix, the offset
961N/A is computed in seconds.
5072N/A </p>
5072N/A<div class="variablelist"><dl>
5072N/A<dt><span class="term">-P <em class="replaceable"><code>date/offset</code></em></span></dt>
5072N/A<dd><p>
5072N/A Sets the date on which a key is to be published to the zone.
5072N/A After that date, the key will be included in the zone but will
5072N/A not be used to sign it. If not set, and if the -G option has
5072N/A not been used, the default is "now".
5072N/A </p></dd>
5072N/A<dt><span class="term">-A <em class="replaceable"><code>date/offset</code></em></span></dt>
5072N/A<dd><p>
5072N/A Sets the date on which the key is to be activated. After that
5072N/A date, the key will be included in the zone and used to sign
5072N/A it. If not set, and if the -G option has not been used, the
5072N/A default is "now".
5072N/A </p></dd>
5072N/A<dt><span class="term">-R <em class="replaceable"><code>date/offset</code></em></span></dt>
5072N/A<dd><p>
5072N/A Sets the date on which the key is to be revoked. After that
5072N/A date, the key will be flagged as revoked. It will be included
5072N/A in the zone and will be used to sign it.
5072N/A </p></dd>
5072N/A<dt><span class="term">-I <em class="replaceable"><code>date/offset</code></em></span></dt>
5072N/A<dd><p>
5072N/A Sets the date on which the key is to be retired. After that
5072N/A date, the key will still be included in the zone, but it
5072N/A will not be used to sign it.
5072N/A </p></dd>
5072N/A<dt><span class="term">-D <em class="replaceable"><code>date/offset</code></em></span></dt>
5072N/A<dd><p>
5072N/A Sets the date on which the key is to be deleted. After that
5072N/A date, the key will no longer be included in the zone. (It
5072N/A may remain in the key repository, however.)
5072N/A </p></dd>
5072N/A</dl></div>
5072N/A</div>
5072N/A<div class="refsect1" lang="en">
5072N/A<a name="id2669588"></a><h2>GENERATED KEY FILES</h2>
5072N/A<p>
5072N/A When <span><strong class="command">dnssec-keyfromlabel</strong></span> completes
1298N/A successfully,
1298N/A it prints a string of the form <code class="filename">Knnnn.+aaa+iiiii</code>
1298N/A to the standard output. This is an identification string for
1298N/A the key files it has generated.
1298N/A </p>
1298N/A<div class="itemizedlist"><ul type="disc">
1298N/A<li><p><code class="filename">nnnn</code> is the key name.
1298N/A </p></li>
1298N/A<li><p><code class="filename">aaa</code> is the numeric representation
1298N/A of the algorithm.
1298N/A </p></li>
1298N/A<li><p><code class="filename">iiiii</code> is the key identifier (or
1298N/A footprint).
1298N/A </p></li>
1298N/A</ul></div>
1298N/A<p><span><strong class="command">dnssec-keyfromlabel</strong></span>
1298N/A creates two files, with names based
1298N/A on the printed string. <code class="filename">Knnnn.+aaa+iiiii.key</code>
1298N/A contains the public key, and
1298N/A <code class="filename">Knnnn.+aaa+iiiii.private</code> contains the
1298N/A private key.
1298N/A </p>
1298N/A<p>
1298N/A The <code class="filename">.key</code> file contains a DNS KEY record
1298N/A that
1298N/A can be inserted into a zone file (directly or with a $INCLUDE
1298N/A statement).
1298N/A </p>
1298N/A<p>
1298N/A The <code class="filename">.private</code> file contains
1298N/A algorithm-specific
1298N/A fields. For obvious security reasons, this file does not have
1298N/A general read permission.
1298N/A </p>
1298N/A</div>
1878N/A<div class="refsect1" lang="en">
1878N/A<a name="id2669682"></a><h2>SEE ALSO</h2>
1298N/A<p><span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>,
1298N/A <span class="citerefentry"><span class="refentrytitle">dnssec-signzone</span>(8)</span>,
1298N/A <em class="citetitle">BIND 9 Administrator Reference Manual</em>,
1298N/A <em class="citetitle">RFC 4034</em>.
1298N/A </p>
1298N/A</div>
1298N/A<div class="refsect1" lang="en">
1298N/A<a name="id2669715"></a><h2>AUTHOR</h2>
1298N/A<p><span class="corpauthor">Internet Systems Consortium</span>
1298N/A </p>
1298N/A</div>
1298N/A</div>
1298N/A<div class="navfooter">
1298N/A<hr>
1298N/A<table width="100%" summary="Navigation footer">
1298N/A<tr>
1298N/A<td width="40%" align="left">
1298N/A<a accesskey="p" href="man.dnssec-dsfromkey.html">Prev</a>�</td>
1298N/A<td width="20%" align="center"><a accesskey="u" href="Bv9ARM.ch10.html">Up</a></td>
6341N/A<td width="40%" align="right">�<a accesskey="n" href="man.dnssec-keygen.html">Next</a>
6341N/A</td>
1298N/A</tr>
1298N/A<tr>
1298N/A<td width="40%" align="left" valign="top">
1298N/A<span class="application">dnssec-dsfromkey</span>�</td>
1298N/A<td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td>
1298N/A<td width="40%" align="right" valign="top">�<span class="application">dnssec-keygen</span>
1298N/A</td>
1298N/A</tr>
1298N/A</table>
1298N/A</div>
1298N/A</body>
1298N/A</html>
1298N/A