man.dnssec-keyfromlabel.html revision 6d382c9fcec316a84a237779fb64bb471b6f9d43
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<!--
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync - Copyright (C) 2004-2014 Internet Systems Consortium, Inc. ("ISC")
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync - Copyright (C) 2000-2003 Internet Software Consortium.
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync -
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync - Permission to use, copy, modify, and/or distribute this software for any
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync - purpose with or without fee is hereby granted, provided that the above
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync - copyright notice and this permission notice appear in all copies.
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync -
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync - PERFORMANCE OF THIS SOFTWARE.
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync-->
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<!-- $Id$ -->
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<html>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<head>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<title>dnssec-keyfromlabel</title>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<link rel="up" href="Bv9ARM.ch10.html" title="Manual pages">
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<link rel="prev" href="man.dnssec-dsfromkey.html" title="dnssec-dsfromkey">
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<link rel="next" href="man.dnssec-keygen.html" title="dnssec-keygen">
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync</head>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<div class="navheader">
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<table width="100%" summary="Navigation header">
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<tr><th colspan="3" align="center"><span class="application">dnssec-keyfromlabel</span></th></tr>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<tr>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<td width="20%" align="left">
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<a accesskey="p" href="man.dnssec-dsfromkey.html">Prev</a>�</td>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<th width="60%" align="center">Manual pages</th>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<td width="20%" align="right">�<a accesskey="n" href="man.dnssec-keygen.html">Next</a>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync</td>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync</tr>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync</table>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<hr>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync</div>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<div class="refentry" lang="en">
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<a name="man.dnssec-keyfromlabel"></a><div class="titlepage"></div>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<div class="refnamediv">
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<h2>Name</h2>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<p><span class="application">dnssec-keyfromlabel</span> &#8212; DNSSEC key generation tool</p>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync</div>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<div class="refsynopsisdiv">
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<h2>Synopsis</h2>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<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>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync</div>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<div class="refsect1" lang="en">
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<a name="id2619042"></a><h2>DESCRIPTION</h2>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<p><span><strong class="command">dnssec-keyfromlabel</strong></span>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync gets keys with the given label from a crypto hardware and builds
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync key files for DNSSEC (Secure DNS), as defined in RFC 2535
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync and RFC 4034.
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync </p>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<p>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync The <code class="option">name</code> of the key is specified on the command
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync line. This must match the name of the zone for which the key is
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync being generated.
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync </p>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync</div>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<div class="refsect1" lang="en">
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<a name="id2619062"></a><h2>OPTIONS</h2>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<div class="variablelist"><dl>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<dt><span class="term">-a <em class="replaceable"><code>algorithm</code></em></span></dt>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<dd>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<p>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync Selects the cryptographic algorithm. The value of
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync <code class="option">algorithm</code> must be one of RSAMD5, RSASHA1,
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync DSA, NSEC3RSASHA1, NSEC3DSA, RSASHA256, RSASHA512, ECCGOST,
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync ECDSAP256SHA256 or ECDSAP384SHA384.
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync These values are case insensitive.
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync </p>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<p>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync If no algorithm is specified, then RSASHA1 will be used by
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync default, unless the <code class="option">-3</code> option is specified,
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync in which case NSEC3RSASHA1 will be used instead. (If
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync <code class="option">-3</code> is used and an algorithm is specified,
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync that algorithm will be checked for compatibility with NSEC3.)
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync </p>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<p>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync Note 1: that for DNSSEC, RSASHA1 is a mandatory to implement
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync algorithm, and DSA is recommended.
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync </p>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<p>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync Note 2: DH automatically sets the -k flag.
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync </p>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync</dd>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<dt><span class="term">-3</span></dt>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<dd><p>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync Use an NSEC3-capable algorithm to generate a DNSSEC key.
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync If this option is used and no algorithm is explicitly
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync set on the command line, NSEC3RSASHA1 will be used by
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync default.
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync </p></dd>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<dt><span class="term">-E <em class="replaceable"><code>engine</code></em></span></dt>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<dd>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<p>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync Specifies the cryptographic hardware to use.
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync </p>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<p>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync When BIND is built with OpenSSL PKCS#11 support, this defaults
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync to the string "pkcs11", which identifies an OpenSSL engine
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync that can drive a cryptographic accelerator or hardware service
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync module. When BIND is built with native PKCS#11 cryptography
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync (--enable-native-pkcs11), it defaults to the path of the PKCS#11
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync provider library specified via "--with-pkcs11".
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync </p>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync</dd>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<dt><span class="term">-l <em class="replaceable"><code>label</code></em></span></dt>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<dd>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<p>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync Specifies the label for a key pair in the crypto hardware.
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync </p>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<p>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync When <acronym class="acronym">BIND</acronym> 9 is built with OpenSSL-based
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync PKCS#11 support, the label is an arbitrary string that
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync identifies a particular key. It may be preceded by an
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync optional OpenSSL engine name, followed by a colon, as in
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync "pkcs11:<em class="replaceable"><code>keylabel</code></em>".
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync </p>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<p>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync When <acronym class="acronym">BIND</acronym> 9 is built with native PKCS#11
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync support, the label is a PKCS#11 URI string in the format
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync "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>]"
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync Keywords include "token", which identifies the HSM; "object", which
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync identifies the key; and "pin-source", which identifies a file from
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync which the HSM's PIN code can be obtained. The label will be
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync stored in the on-disk "private" file.
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync </p>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<p>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync If the label contains a
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync <code class="option">pin-source</code> field, tools using the generated
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync key files will be able to use the HSM for signing and other
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync operations without any need for an operator to manually enter
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync a PIN. Note: Making the HSM's PIN accessible in this manner
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync may reduce the security advantage of using an HSM; be sure
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync this is what you want to do before making use of this feature.
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync </p>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync</dd>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<dt><span class="term">-n <em class="replaceable"><code>nametype</code></em></span></dt>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<dd><p>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync Specifies the owner type of the key. The value of
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync <code class="option">nametype</code> must either be ZONE (for a DNSSEC
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync zone key (KEY/DNSKEY)), HOST or ENTITY (for a key associated with
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync a host (KEY)),
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync USER (for a key associated with a user(KEY)) or OTHER (DNSKEY).
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync These values are case insensitive.
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync </p></dd>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<dt><span class="term">-C</span></dt>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<dd><p>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync Compatibility mode: generates an old-style key, without
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync any metadata. By default, <span><strong class="command">dnssec-keyfromlabel</strong></span>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync will include the key's creation date in the metadata stored
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync with the private key, and other dates may be set there as well
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync (publication date, activation date, etc). Keys that include
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync this data may be incompatible with older versions of BIND; the
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync <code class="option">-C</code> option suppresses them.
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync </p></dd>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<dt><span class="term">-c <em class="replaceable"><code>class</code></em></span></dt>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync<dd><p>
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync Indicates that the DNS record containing the key should have
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync the specified class. If not specified, class IN is used.
</p></dd>
<dt><span class="term">-f <em class="replaceable"><code>flag</code></em></span></dt>
<dd><p>
Set the specified flag in the flag field of the KEY/DNSKEY record.
The only recognized flags are KSK (Key Signing Key) and REVOKE.
</p></dd>
<dt><span class="term">-G</span></dt>
<dd><p>
Generate a key, but do not publish it or sign with it. This
option is incompatible with -P and -A.
</p></dd>
<dt><span class="term">-h</span></dt>
<dd><p>
Prints a short summary of the options and arguments to
<span><strong class="command">dnssec-keyfromlabel</strong></span>.
</p></dd>
<dt><span class="term">-K <em class="replaceable"><code>directory</code></em></span></dt>
<dd><p>
Sets the directory in which the key files are to be written.
</p></dd>
<dt><span class="term">-k</span></dt>
<dd><p>
Generate KEY records rather than DNSKEY records.
</p></dd>
<dt><span class="term">-L <em class="replaceable"><code>ttl</code></em></span></dt>
<dd><p>
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.
</p></dd>
<dt><span class="term">-p <em class="replaceable"><code>protocol</code></em></span></dt>
<dd><p>
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.
</p></dd>
<dt><span class="term">-t <em class="replaceable"><code>type</code></em></span></dt>
<dd><p>
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.
</p></dd>
<dt><span class="term">-v <em class="replaceable"><code>level</code></em></span></dt>
<dd><p>
Sets the debugging level.
</p></dd>
<dt><span class="term">-y</span></dt>
<dd><p>
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.)
</p></dd>
</dl></div>
</div>
<div class="refsect1" lang="en">
<a name="id2619499"></a><h2>TIMING OPTIONS</h2>
<p>
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'.
</p>
<div class="variablelist"><dl>
<dt><span class="term">-P <em class="replaceable"><code>date/offset</code></em></span></dt>
<dd><p>
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".
</p></dd>
<dt><span class="term">-A <em class="replaceable"><code>date/offset</code></em></span></dt>
<dd><p>
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
default is "now".
</p></dd>
<dt><span class="term">-R <em class="replaceable"><code>date/offset</code></em></span></dt>
<dd><p>
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.
</p></dd>
<dt><span class="term">-I <em class="replaceable"><code>date/offset</code></em></span></dt>
<dd><p>
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.
</p></dd>
<dt><span class="term">-D <em class="replaceable"><code>date/offset</code></em></span></dt>
<dd><p>
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.)
</p></dd>
</dl></div>
</div>
<div class="refsect1" lang="en">
<a name="id2670797"></a><h2>GENERATED KEY FILES</h2>
<p>
When <span><strong class="command">dnssec-keyfromlabel</strong></span> completes
successfully,
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.
</p>
<div class="itemizedlist"><ul type="disc">
<li><p><code class="filename">nnnn</code> is the key name.
</p></li>
<li><p><code class="filename">aaa</code> is the numeric representation
of the algorithm.
</p></li>
<li><p><code class="filename">iiiii</code> is the key identifier (or
footprint).
</p></li>
</ul></div>
<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
private key.
</p>
<p>
The <code class="filename">.key</code> file contains a DNS KEY record
that
can be inserted into a zone file (directly or with a $INCLUDE
statement).
</p>
<p>
The <code class="filename">.private</code> file contains
algorithm-specific
fields. For obvious security reasons, this file does not have
general read permission.
</p>
</div>
<div class="refsect1" lang="en">
<a name="id2670891"></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>.
</p>
</div>
<div class="refsect1" lang="en">
<a name="id2670929"></a><h2>AUTHOR</h2>
<p><span class="corpauthor">Internet Systems Consortium</span>
</p>
</div>
</div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left">
<a accesskey="p" href="man.dnssec-dsfromkey.html">Prev</a>�</td>
<td width="20%" align="center"><a accesskey="u" href="Bv9ARM.ch10.html">Up</a></td>
<td width="40%" align="right">�<a accesskey="n" href="man.dnssec-keygen.html">Next</a>
</td>
</tr>
<tr>
<td width="40%" align="left" valign="top">
<span class="application">dnssec-dsfromkey</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>
</td>
</tr>
</table>
</div>
</body>
</html>