From 453f5da79000b2d6b57b43c663337ad26a1bd15c Mon Sep 17 00:00:00 2001
From: Tinderbox User
Date: Thu, 21 Feb 2019 02:11:15 +0000
Subject: [PATCH] doc rebuild
---
bin/python/dnssec-keymgr.8 | 36 ++++++++-------
bin/python/dnssec-keymgr.html | 62 +++++++++++++++-----------
config.h.in | 2 +-
doc/arm/Bv9ARM.ch01.html | 2 +-
doc/arm/Bv9ARM.ch02.html | 2 +-
doc/arm/Bv9ARM.ch03.html | 2 +-
doc/arm/Bv9ARM.ch04.html | 2 +-
doc/arm/Bv9ARM.ch05.html | 29 +++++++++++-
doc/arm/Bv9ARM.ch06.html | 2 +-
doc/arm/Bv9ARM.ch07.html | 2 +-
doc/arm/Bv9ARM.ch08.html | 31 +++++++++++--
doc/arm/Bv9ARM.ch09.html | 2 +-
doc/arm/Bv9ARM.ch10.html | 2 +-
doc/arm/Bv9ARM.ch11.html | 2 +-
doc/arm/Bv9ARM.ch12.html | 2 +-
doc/arm/Bv9ARM.html | 6 +--
doc/arm/Bv9ARM.pdf | Bin 1090953 -> 1092272 bytes
doc/arm/man.arpaname.html | 2 +-
doc/arm/man.ddns-confgen.html | 2 +-
doc/arm/man.delv.html | 2 +-
doc/arm/man.dig.html | 2 +-
doc/arm/man.dnssec-cds.html | 2 +-
doc/arm/man.dnssec-checkds.html | 2 +-
doc/arm/man.dnssec-coverage.html | 2 +-
doc/arm/man.dnssec-dsfromkey.html | 2 +-
doc/arm/man.dnssec-importkey.html | 2 +-
doc/arm/man.dnssec-keyfromlabel.html | 2 +-
doc/arm/man.dnssec-keygen.html | 2 +-
doc/arm/man.dnssec-keymgr.html | 64 ++++++++++++++++-----------
doc/arm/man.dnssec-revoke.html | 2 +-
doc/arm/man.dnssec-settime.html | 2 +-
doc/arm/man.dnssec-signzone.html | 2 +-
doc/arm/man.dnssec-verify.html | 2 +-
doc/arm/man.dnstap-read.html | 2 +-
doc/arm/man.filter-aaaa.html | 2 +-
doc/arm/man.host.html | 2 +-
doc/arm/man.mdig.html | 2 +-
doc/arm/man.named-checkconf.html | 2 +-
doc/arm/man.named-checkzone.html | 2 +-
doc/arm/man.named-journalprint.html | 2 +-
doc/arm/man.named-nzd2nzf.html | 2 +-
doc/arm/man.named-rrchecker.html | 2 +-
doc/arm/man.named.conf.html | 2 +-
doc/arm/man.named.html | 2 +-
doc/arm/man.nsec3hash.html | 2 +-
doc/arm/man.nslookup.html | 2 +-
doc/arm/man.nsupdate.html | 2 +-
doc/arm/man.pkcs11-destroy.html | 2 +-
doc/arm/man.pkcs11-keygen.html | 2 +-
doc/arm/man.pkcs11-list.html | 2 +-
doc/arm/man.pkcs11-tokens.html | 2 +-
doc/arm/man.rndc-confgen.html | 2 +-
doc/arm/man.rndc.conf.html | 2 +-
doc/arm/man.rndc.html | 2 +-
doc/arm/notes.html | 27 ++++++++++-
doc/arm/notes.pdf | Bin 84969 -> 85395 bytes
doc/arm/notes.txt | 16 ++++++-
57 files changed, 241 insertions(+), 124 deletions(-)
diff --git a/bin/python/dnssec-keymgr.8 b/bin/python/dnssec-keymgr.8
index 3f39fd408d..4a658dbe88 100644
--- a/bin/python/dnssec-keymgr.8
+++ b/bin/python/dnssec-keymgr.8
@@ -49,7 +49,7 @@ and
\fBdnssec\-settime\fR\&.
.PP
DNSSEC policy can be read from a configuration file (default
-/etc/dnssec\-policy\&.conf), 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\&.
+/etc/dnssec\-policy\&.conf), 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\&.
.PP
When
\fBdnssec\-keymgr\fR
@@ -181,7 +181,8 @@ would be used for zones that had unusually high security needs\&.
.sp -1
.IP \(bu 2.3
.\}
-Algorithm policies: (\fBalgorithm\-policy \fR\fB\fIalgorithm\fR\fR\fB { \&.\&.\&. };\fR
+\fIAlgorithm policies:\fR
+(\fBalgorithm\-policy \fR\fB\fIalgorithm\fR\fR\fB { \&.\&.\&. };\fR
) 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
\fBalgorithm\-policy\fR, and the new key sizes would then be used for any key of type RSASHA256\&.
.RE
@@ -194,59 +195,60 @@ Algorithm policies: (\fBalgorithm\-policy \fR\fB\fIalgorithm\fR\fR\fB { \&.\&.\&
.sp -1
.IP \(bu 2.3
.\}
-Zone policies: (\fBzone \fR\fB\fIname\fR\fR\fB { \&.\&.\&. };\fR
+\fIZone policies:\fR
+(\fBzone \fR\fB\fIname\fR\fR\fB { \&.\&.\&. };\fR
) set policy for a single zone by name\&. A zone policy can inherit a policy class by including a
\fBpolicy\fR
-option\&. Zone names beginning with digits (i\&.e\&., 0\-9) must be quoted\&.
+option\&. Zone names beginning with digits (i\&.e\&., 0\-9) must be quoted\&. If a zone does not have its own policy then the "default" policy applies\&.
.RE
.PP
Options that can be specified in policies:
.PP
-\fBalgorithm\fR
+\fBalgorithm\fR \fIname\fR;
.RS 4
The key algorithm\&. If no policy is defined, the default is RSASHA256\&.
.RE
.PP
-\fBcoverage\fR
+\fBcoverage\fR \fIduration\fR;
.RS 4
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\&.
.RE
.PP
-\fBdirectory\fR
+\fBdirectory\fR \fIpath\fR;
.RS 4
Specifies the directory in which keys should be stored\&.
.RE
.PP
-\fBkey\-size\fR
+\fBkey\-size\fR \fIkeytype\fR \fIsize\fR;
.RS 4
-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 2048 bits for RSA keys\&.
+Specifies the number of bits to use in creating keys\&. The keytype is either "zsk" or "ksk"\&. 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 2048 bits for RSA keys\&.
.RE
.PP
-\fBkeyttl\fR
+\fBkeyttl\fR \fIduration\fR;
.RS 4
The key TTL\&. If no policy is defined, the default is one hour\&.
.RE
.PP
-\fBpost\-publish\fR
+\fBpost\-publish\fR \fIkeytype\fR \fIduration\fR;
.RS 4
How long after inactivation a key should be deleted from the zone\&. Note: If
\fBroll\-period\fR
-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\&.
+is not set, this value is ignored\&. The keytype is either "zsk" or "ksk"\&. A default duration for this option can be set in algorithm policies as well as in policy classes or zone policies\&. The default is one month\&.
.RE
.PP
-\fBpre\-publish\fR
+\fBpre\-publish\fR \fIkeytype\fR \fIduration\fR;
.RS 4
How long before activation a key should be published\&. Note: If
\fBroll\-period\fR
-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\&.
+is not set, this value is ignored\&. The keytype is either "zsk" or "ksk"\&. A default duration for this option can be set in algorithm policies as well as in policy classes or zone policies\&. The default is one month\&.
.RE
.PP
-\fBroll\-period\fR
+\fBroll\-period\fR \fIkeytype\fR \fIduration\fR;
.RS 4
-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\*(Aqs\&. KSK\*(Aqs do not roll over by default\&.
+How frequently keys should be rolled over\&. The keytype is either "zsk" or "ksk"\&. A default duration 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 ZSKs\&. KSKs do not roll over by default\&.
.RE
.PP
-\fBstandby\fR
+\fBstandby\fR \fIkeytype\fR \fInumber\fR;
.RS 4
Not yet implemented\&.
.RE
diff --git a/bin/python/dnssec-keymgr.html b/bin/python/dnssec-keymgr.html
index b9a0a0beb1..564dab7b19 100644
--- a/bin/python/dnssec-keymgr.html
+++ b/bin/python/dnssec-keymgr.html
@@ -57,11 +57,12 @@
DNSSEC policy can be read from a configuration file (default
- /etc/dnssec-policy.conf), from which the key
- parameters, publication and rollover schedule, and desired
- coverage duration for any given zone can be determined. This
+ /etc/dnssec-policy.conf), 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.
+ per-zone basis, or to set a "default" policy
+ used for all zones.
When dnssec-keymgr runs, it examines the DNSSEC
@@ -210,7 +211,7 @@
- Algorithm policies:
+ Algorithm policies:
(algorithm-policy algorithm { ... }; )
override default per-algorithm settings. For example, by default,
RSASHA256 keys use 2048-bit key sizes for both KSK and ZSK. This
@@ -220,11 +221,13 @@
- Zone policies:
+ Zone policies:
(zone name { ... }; )
set policy for a single zone by name. A zone policy can inherit
a policy class by including a policy option.
Zone names beginning with digits (i.e., 0-9) must be quoted.
+ If a zone does not have its own policy then the
+ "default" policy applies.
@@ -232,81 +235,90 @@
Options that can be specified in policies:
-- algorithm
+- algorithm
+
name;
-
The key algorithm. If no policy is defined, the default is
RSASHA256.
-- coverage
+- coverage
+
duration;
-
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").
+ 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.
-- directory
+- directory
+
path;
-
Specifies the directory in which keys should be stored.
-- key-size
+- key-size
keytype
+ size;
-
Specifies the number of bits to use in creating keys.
- Takes two arguments: keytype (eihter "zsk" or "ksk") and size.
+ The keytype is either "zsk" or "ksk".
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 2048 bits for RSA keys.
-- keyttl
+- keyttl
+
duration;
-
The key TTL. If no policy is defined, the default is one hour.
-- post-publish
+- post-publish
keytype
+ duration;
-
How long after inactivation a key should be deleted from the zone.
Note: If roll-period 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
+ ignored. The keytype is either "zsk" or "ksk".
+ A default duration for this option can be set in algorithm
policies as well as in policy classes or zone policies. The default
is one month.
-- pre-publish
+- pre-publish
keytype
+ duration;
-
How long before activation a key should be published. Note: If
roll-period 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
+ The keytype is either "zsk" or "ksk".
+ A default duration for this option can be set in algorithm policies
as well as in policy classes or zone policies. The default is
one month.
-- roll-period
+- roll-period
keytype
+ duration;
-
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
+ The keytype is either "zsk" or "ksk".
+ A default duration 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
+ configured, the default is one year for ZSKs. KSKs do not
roll over by default.
-- standby
+- standby
keytype
+ number;
-
Not yet implemented.
diff --git a/config.h.in b/config.h.in
index 4ac8bf5e86..dd6598aa98 100644
--- a/config.h.in
+++ b/config.h.in
@@ -60,7 +60,7 @@
/* Define if clock_gettime is available. */
#undef HAVE_CLOCK_GETTIME
-/* Use cmocka */
+/* Use CMocka */
#undef HAVE_CMOCKA
/* Define to 1 if you have the `cpuset_setaffinity' function. */
diff --git a/doc/arm/Bv9ARM.ch01.html b/doc/arm/Bv9ARM.ch01.html
index 6d08a7d642..66ed40f1d1 100644
--- a/doc/arm/Bv9ARM.ch01.html
+++ b/doc/arm/Bv9ARM.ch01.html
@@ -614,6 +614,6 @@
-BIND 9.13.6 (Development Release)
+BIND 9.13.7 (Development Release)