dnssec-settime.html revision 794b79e6bbc3f5db1ea6ae154d739b9f1ef1a375
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp - Copyright (C) 2009-2011, 2014 Internet Systems Consortium, Inc. ("ISC")
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp - Permission to use, copy, modify, and/or distribute this software for any
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp - purpose with or without fee is hereby granted, provided that the above
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp - copyright notice and this permission notice appear in all copies.
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp - PERFORMANCE OF THIS SOFTWARE.
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp<!-- $Id$ -->
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en">
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp<a name="man.dnssec-settime"></a><div class="titlepage"></div>
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp<p><span class="application">dnssec-settime</span> — Set the key timing metadata for a DNSSEC key</p>
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp<div class="cmdsynopsis"><p><code class="command">dnssec-settime</code> [<code class="option">-f</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">-P <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-A <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-R <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-I <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-D <em class="replaceable"><code>date/offset</code></em></code>] [<code class="option">-h</code>] [<code class="option">-v <em class="replaceable"><code>level</code></em></code>] [<code class="option">-E <em class="replaceable"><code>engine</code></em></code>] {keyfile}</p></div>
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp<p><span><strong class="command">dnssec-settime</strong></span>
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp reads a DNSSEC private key file and sets the key timing metadata
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp as specified by the <code class="option">-P</code>, <code class="option">-A</code>,
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp <code class="option">-R</code>, <code class="option">-I</code>, and <code class="option">-D</code>
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp options. The metadata can then be used by
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp <span><strong class="command">dnssec-signzone</strong></span> or other signing software to
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp determine when a key is to be published, whether it should be
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp used for signing a zone, etc.
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp If none of these options is set on the command line,
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp then <span><strong class="command">dnssec-settime</strong></span> simply prints the key timing
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp metadata already stored in the key.
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp When key metadata fields are changed, both files of a key
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp pair (<code class="filename">Knnnn.+aaa+iiiii.key</code> and
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp <code class="filename">Knnnn.+aaa+iiiii.private</code>) are regenerated.
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp Metadata fields are stored in the private file. A human-readable
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp description of the metadata is also placed in comments in the key
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp file. The private file's permissions are always set to be
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp inaccessible to anyone other than the owner (mode 0600).
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp Force an update of an old-format key with no metadata fields.
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp Without this option, <span><strong class="command">dnssec-settime</strong></span> will
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp fail when attempting to update a legacy key. With this option,
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp the key will be recreated in the new format, but with the
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp original key data retained. The key's creation date will be
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp set to the present time. If no other values are specified,
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp then the key's publication and activation dates will also
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp be set to the present time.
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp<dt><span class="term">-K <em class="replaceable"><code>directory</code></em></span></dt>
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp Sets the directory in which the key files are to reside.
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp<dt><span class="term">-L <em class="replaceable"><code>ttl</code></em></span></dt>
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp Sets the default TTL to use for this key when it is converted
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp into a DNSKEY RR. If the key is imported into a zone,
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp this is the TTL that will be used for it, unless there was
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp already a DNSKEY RRset in place, in which case the existing TTL
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp would take precedence. Setting the default TTL to
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp <code class="literal">0</code> or <code class="literal">none</code> removes it.
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp Emit usage message and exit.
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp<dt><span class="term">-v <em class="replaceable"><code>level</code></em></span></dt>
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp Sets the debugging level.
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp<dt><span class="term">-E <em class="replaceable"><code>engine</code></em></span></dt>
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp Specifies the cryptographic hardware to use, when applicable.
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp When BIND is built with OpenSSL PKCS#11 support, this defaults
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp to the string "pkcs11", which identifies an OpenSSL engine
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp that can drive a cryptographic accelerator or hardware service
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp module. When BIND is built with native PKCS#11 cryptography
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp (--enable-native-pkcs11), it defaults to the path of the PKCS#11
eb0cc229f19c437a6b538d3ac0d0443268290b7eedp provider library specified via "--with-pkcs11".