Gecko [ nbspublicschool.com ]

Name	Size	Permission
sample	[ DIR ]	drwxr-xr-x
Bv9ARM.ch01.html	26.11 KB	-rw-r--r--
Bv9ARM.ch02.html	7.18 KB	-rw-r--r--
Bv9ARM.ch03.html	30.38 KB	-rw-r--r--
Bv9ARM.ch04.html	129.65 KB	-rw-r--r--
Bv9ARM.ch05.html	6.29 KB	-rw-r--r--
Bv9ARM.ch06.html	684.15 KB	-rw-r--r--
Bv9ARM.ch07.html	19.56 KB	-rw-r--r--
Bv9ARM.ch08.html	6.32 KB	-rw-r--r--
Bv9ARM.ch09.html	10.27 KB	-rw-r--r--
Bv9ARM.ch10.html	6.92 KB	-rw-r--r--
Bv9ARM.ch11.html	53.24 KB	-rw-r--r--
Bv9ARM.ch12.html	20.45 KB	-rw-r--r--
Bv9ARM.ch13.html	9.88 KB	-rw-r--r--
Bv9ARM.html	29.71 KB	-rw-r--r--
Bv9ARM.pdf	1.24 MB	-rw-r--r--
CHANGES	528.76 KB	-rw-r--r--
README	22.46 KB	-rw-r--r--
isc-logo.pdf	281.24 KB	-rw-r--r--
man.arpaname.html	3.01 KB	-rw-r--r--
man.ddns-confgen.html	9.49 KB	-rw-r--r--
man.delv.html	23.87 KB	-rw-r--r--
man.dig.html	40.63 KB	-rw-r--r--
man.dnssec-checkds.html	5.35 KB	-rw-r--r--
man.dnssec-coverage.html	11.35 KB	-rw-r--r--
man.dnssec-dsfromkey.html	9.68 KB	-rw-r--r--
man.dnssec-importkey.html	9.58 KB	-rw-r--r--
man.dnssec-keyfromlabel.html	19.12 KB	-rw-r--r--
man.dnssec-keygen.html	22.31 KB	-rw-r--r--
man.dnssec-keymgr.html	15.15 KB	-rw-r--r--
man.dnssec-revoke.html	5.62 KB	-rw-r--r--
man.dnssec-settime.html	14.55 KB	-rw-r--r--
man.dnssec-signzone.html	30.69 KB	-rw-r--r--
man.dnssec-verify.html	7.43 KB	-rw-r--r--
man.dnstap-read.html	4.39 KB	-rw-r--r--
man.genrandom.html	4.13 KB	-rw-r--r--
man.host.html	12.74 KB	-rw-r--r--
man.isc-hmac-fixup.html	4.6 KB	-rw-r--r--
man.lwresd.html	12.45 KB	-rw-r--r--
man.mdig.html	23.18 KB	-rw-r--r--
man.named-checkconf.html	6.77 KB	-rw-r--r--
man.named-checkzone.html	20.21 KB	-rw-r--r--
man.named-journalprint.html	4.2 KB	-rw-r--r--
man.named-nzd2nzf.html	3.86 KB	-rw-r--r--
man.named-rrchecker.html	4.21 KB	-rw-r--r--
man.named.conf.html	73.42 KB	-rw-r--r--
man.named.html	19.07 KB	-rw-r--r--
man.nsec3hash.html	4.17 KB	-rw-r--r--
man.nslookup.html	14.49 KB	-rw-r--r--
man.nsupdate.html	28.11 KB	-rw-r--r--
man.pkcs11-destroy.html	5.57 KB	-rw-r--r--
man.pkcs11-keygen.html	7.13 KB	-rw-r--r--
man.pkcs11-list.html	5.46 KB	-rw-r--r--
man.pkcs11-tokens.html	3.73 KB	-rw-r--r--
man.rndc-confgen.html	11.48 KB	-rw-r--r--
man.rndc.conf.html	10.17 KB	-rw-r--r--
man.rndc.html	39.89 KB	-rw-r--r--
named.conf.default	1.76 KB	-rw-r--r--
notes.html	7.31 KB	-rw-r--r--
notes.pdf	50.96 KB	-rw-r--r--

Code Editor : man.dnssec-keymgr.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">

<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-keymgr</title>
<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.dnssec-keygen.html" title="dnssec-keygen">
<link rel="next" href="man.dnssec-revoke.html" title="dnssec-revoke">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<div class="navheader">
<table width="100%" summary="Navigation header">
<tr><th colspan="3" align="center">dnssec-keymgr</th></tr>
<tr>
<td width="20%" align="left">
<a accesskey="p" href="man.dnssec-keygen.html">Prev</a>�</td>
<th width="60%" align="center">Manual pages</th>
<td width="20%" align="right">�<a accesskey="n" href="man.dnssec-revoke.html">Next</a>
</td>
</tr>
</table>
<hr>
</div>
<div class="refentry">
<a name="man.dnssec-keymgr"></a><div class="titlepage"></div>

<div class="refnamediv">
<h2>Name</h2>

 dnssec-keymgr
 &#8212; Ensures correct DNSKEY coverage for a zone based on a defined policy
 
</div>

<div class="refsynopsisdiv">
<h2>Synopsis</h2>
 <div class="cmdsynopsis">
 <code class="command">dnssec-keymgr</code> 
 [<code class="option">-K <code>directory</code></code>]
 [<code class="option">-c <code>file</code></code>]
 [<code class="option">-f</code>]
 [<code class="option">-k</code>]
 [<code class="option">-q</code>]
 [<code class="option">-v</code>]
 [<code class="option">-z</code>]
 [<code class="option">-g <code>path</code></code>]
 [<code class="option">-r <code>path</code></code>]
 [<code class="option">-s <code>path</code></code>]
 [zone...]
 </div>
 </div>

<div class="refsection">
<a name="id-1.14.13.7"></a><h2>DESCRIPTION</h2>
 
 dnssec-keymgr is a high level Python wrapper
 to facilitate the key rollover process for zones handled by
 BIND. It uses the BIND commands for manipulating DNSSEC key
 metadata: dnssec-keygen and
 dnssec-settime.
 
 
 DNSSEC policy can be read from a configuration file (default
 <code class="filename">/etc/dnssec-policy.conf</code>), from which the key
 parameters, publication and rollover schedule, and desired
 coverage duration for any given zone can be determined. This
 file may be used to define individual DNSSEC policies on a
 per-zone basis, or to set a default policy used for all zones.
 
 
 When dnssec-keymgr runs, it examines the DNSSEC
 keys for one or more zones, comparing their timing metadata against
 the policies for those zones. If key settings do not conform to the
 DNSSEC policy (for example, because the policy has been changed),
 they are automatically corrected.
 
 
 A zone policy can specify a duration for which we want to
 ensure the key correctness (<code class="option">coverage</code>). It can
 also specify a rollover period (<code class="option">roll-period</code>).
 If policy indicates that a key should roll over before the
 coverage period ends, then a successor key will automatically be
 created and added to the end of the key series.
 
 
 If zones are specified on the command line,
 dnssec-keymgr will examine only those zones.
 If a specified zone does not already have keys in place, then
 keys will be generated for it according to policy.
 
 
 If zones are not specified on the command
 line, then dnssec-keymgr will search the
 key directory (either the current working directory or the directory
 set by the <code class="option">-K</code> option), and check the keys for
 all the zones represented in the directory.
 
 
 It is expected that this tool will be run automatically and
 unattended (for example, by cron).
 
 </div>

<div class="refsection">
<a name="id-1.14.13.8"></a><h2>OPTIONS</h2>
 <div class="variablelist"><dl class="variablelist">
<dt>-c <code>file</code></dt>
<dd>
	 
	 If <code class="option">-c</code> is specified, then the DNSSEC
	 policy is read from <code class="option">file</code>. (If not
	 specified, then the policy is read from
	 <code class="filename">/etc/dnssec-policy.conf</code>; if that file
	 doesn't exist, a built-in global default policy is used.)
	 
	</dd>
<dt>-f</dt>
<dd>
	 
	 Force: allow updating of key events even if they are
	 already in the past. This is not recommended for use with
	 zones in which keys have already been published. However,
	 if a set of keys has been generated all of which have
	 publication and activation dates in the past, but the
	 keys have not been published in a zone as yet, then this
	 option can be used to clean them up and turn them into a
	 proper series of keys with appropriate rollover intervals.
	 
	</dd>
<dt>-g <code>keygen-path</code></dt>
<dd>
	 
	 Specifies a path to a dnssec-keygen binary.
	 Used for testing.
	 See also the <code class="option">-s</code> option.
	 
	</dd>
<dt>-h</dt>
<dd>
	 
	 Print the dnssec-keymgr help summary
	 and exit.
	 
	</dd>
<dt>-K <code>directory</code></dt>
<dd>
	 
	 Sets the directory in which keys can be found. Defaults to the
	 current working directory.
	 
	</dd>
<dt>-k</dt>
<dd>
	 
	 Only apply policies to KSK keys.
	 See also the <code class="option">-z</code> option.
	 
	</dd>
<dt>-q</dt>
<dd>
	 
	 Quiet: suppress printing of dnssec-keygen
	 and dnssec-settime.
	 
	</dd>
<dt>-r <code>randomdev</code></dt>
<dd>
	 
	 Specifies a path to a file containing random data.
	 This is passed to the dnssec-keygen binary
	 using its <code class="option">-r</code> option.

</dd>
<dt>-s <code>settime-path</code></dt>
<dd>
	 
	 Specifies a path to a dnssec-settime binary.
	 Used for testing.
	 See also the <code class="option">-g</code> option.
	 
	</dd>
<dt>-v</dt>
<dd>
	 
	 Print the dnssec-keymgr version and exit.
	 
	</dd>
<dt>-z</dt>
<dd>
	 
	 Only apply policies to ZSK keys.
	 See also the <code class="option">-k</code> option.
	 
	</dd>
</dl></div>
 </div>

<div class="refsection">
<a name="id-1.14.13.9"></a><h2>POLICY CONFIGURATION</h2>
 
 The <code class="filename">dnssec-policy.conf</code> file can specify three kinds
 of policies:
 
 <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
<li class="listitem">
	
	 Policy classes
	 (<code class="option">policy <code>name</code> { ... };</code>)
	 can be inherited by zone policies or other policy classes; these
	 can be used to create sets of different security profiles. For
	 example, a policy class <code>normal</code> might specify
	 1024-bit key sizes, but a class <code>extra</code> might
	 specify 2048 bits instead; <code>extra</code> would be
	 used for zones that had unusually high security needs.
	
 </li>
<li class="listitem">
	
	 Algorithm policies:
	 (<code class="option">algorithm-policy <code>algorithm</code> { ... };</code> )
	 override default per-algorithm settings. For example, by default,
	 RSASHA256 keys use 2048-bit key sizes for both KSK and ZSK. This
	 can be modified using algorithm-policy, and the
	 new key sizes would then be used for any key of type RSASHA256.
	
 </li>
<li class="listitem">
	
	 Zone policies:
	 (<code class="option">zone <code>name</code> { ... };</code> )
	 set policy for a single zone by name. A zone policy can inherit
	 a policy class by including a <code class="option">policy</code> option.
	 Zone names beginning with digits (i.e., 0-9) must be quoted.
	
 </li>
</ul></div>
 
 Options that can be specified in policies:
 
 <div class="variablelist"><dl class="variablelist">
<dt>algorithm</dt>
<dd>
	 
	 The key algorithm. If no policy is defined, the default is
	 RSASHA256.
	 
	</dd>
<dt>coverage</dt>
<dd>
	 
	 The length of time to ensure that keys will be correct; no action
	 will be taken to create new keys to be activated after this time.
	 This can be represented as a number of seconds, or as a duration using
	 human-readable units (examples: "1y" or "6 months").
	 A default value for this option can be set in algorithm policies
	 as well as in policy classes or zone policies.
	 If no policy is configured, the default is six months.
	 
	</dd>
<dt>directory</dt>
<dd>
	 
	 Specifies the directory in which keys should be stored.
	 
	</dd>
<dt>key-size</dt>
<dd>
	 
	 Specifies the number of bits to use in creating keys.
	 Takes two arguments: keytype (eihter "zsk" or "ksk") and size.
	 A default value for this option can be set in algorithm policies
	 as well as in policy classes or zone policies. If no policy is
	 configured, the default is 1024 bits for DSA keys and 2048 for
	 RSA.
	 
	</dd>
<dt>keyttl</dt>
<dd>
	 
	 The key TTL. If no policy is defined, the default is one hour.
	 
	</dd>
<dt>post-publish</dt>
<dd>
	 
	 How long after inactivation a key should be deleted from the zone.
	 Note: If <code class="option">roll-period</code> is not set, this value is
	 ignored. Takes two arguments: keytype (eihter "zsk" or "ksk") and a
	 duration. A default value for this option can be set in algorithm
	 policies as well as in policy classes or zone policies. The default
	 is one month.
	 
	</dd>
<dt>pre-publish</dt>
<dd>
	 
	 How long before activation a key should be published. Note: If
	 <code class="option">roll-period</code> is not set, this value is ignored.
	 Takes two arguments: keytype (either "zsk" or "ksk") and a duration.
	 A default value for this option can be set in algorithm policies
	 as well as in policy classes or zone policies. The default is
	 one month.
	 
	</dd>
<dt>roll-period</dt>
<dd>
	 
	 How frequently keys should be rolled over.
	 Takes two arguments: keytype (eihter "zsk" or "ksk") and a duration.
	 A default value for this option can be set in algorithm policies
	 as well as in policy classes or zone policies. If no policy is
	 configured, the default is one year for ZSK's. KSK's do not
	 roll over by default.
	 
	</dd>
<dt>standby</dt>
<dd>
	 
	 Not yet implemented.
	 
	</dd>
</dl></div>
 </div>

<div class="refsection">
<a name="id-1.14.13.10"></a><h2>REMAINING WORK</h2>
 <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
<li class="listitem">
 
	Enable scheduling of KSK rollovers using the <code class="option">-P sync</code>
	and <code class="option">-D sync</code> options to
	dnssec-keygen and
	dnssec-settime. Check the parent zone
	(as in dnssec-checkds) to determine when it's
	safe for the key to roll.
 
 </li>
<li class="listitem">
 
	Allow configuration of standby keys and use of the REVOKE bit,
	for keys that use RFC 5011 semantics.
 
 </li>
</ul></div>
 </div>

<div class="refsection">
<a name="id-1.14.13.11"></a><h2>SEE ALSO</h2>
 
 
	dnssec-coverage(8)
 ,
 
	dnssec-keygen(8)
 ,
 
	dnssec-settime(8)
 ,
 
	dnssec-checkds(8)
 
 
 </div>

</div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left">
<a accesskey="p" href="man.dnssec-keygen.html">Prev</a>�</td>
<td width="20%" align="center"><a accesskey="u" href="Bv9ARM.ch13.html">Up</a></td>
<td width="40%" align="right">�<a accesskey="n" href="man.dnssec-revoke.html">Next</a>
</td>
</tr>
<tr>
<td width="40%" align="left" valign="top">
dnssec-keygen�</td>
<td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td>
<td width="40%" align="right" valign="top">�dnssec-revoke
</td>
</tr>
</table>
</div>
BIND 9.11.4-P2 (Extended Support Version)
</body>
</html>

${this.title}

Code Editor : man.dnssec-keymgr.html