ecb246eba6
the problems related to the handling of broken DNSSEC trust chains. This fix is only relevant for those who have DNSSEC validation enabled and configure trust anchors from third parties, either manually, or through a system like DLV.
205 lines
6.9 KiB
Groff
205 lines
6.9 KiB
Groff
.\" Copyright (C) 2004, 2005, 2007-2010 Internet Systems Consortium, Inc. ("ISC")
|
|
.\" Copyright (C) 2000-2003 Internet Software Consortium.
|
|
.\"
|
|
.\" Permission to use, copy, modify, and/or distribute this software for any
|
|
.\" purpose with or without fee is hereby granted, provided that the above
|
|
.\" copyright notice and this permission notice appear in all copies.
|
|
.\"
|
|
.\" THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
|
|
.\" REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
|
|
.\" AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
|
|
.\" INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
|
|
.\" LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
|
|
.\" OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
|
|
.\" PERFORMANCE OF THIS SOFTWARE.
|
|
.\"
|
|
.\" $Id: dnssec-keygen.8,v 1.40.44.4 2010/01/16 01:55:32 tbox Exp $
|
|
.\"
|
|
.hy 0
|
|
.ad l
|
|
.\" Title: dnssec\-keygen
|
|
.\" Author:
|
|
.\" Generator: DocBook XSL Stylesheets v1.71.1 <http://docbook.sf.net/>
|
|
.\" Date: June 30, 2000
|
|
.\" Manual: BIND9
|
|
.\" Source: BIND9
|
|
.\"
|
|
.TH "DNSSEC\-KEYGEN" "8" "June 30, 2000" "BIND9" "BIND9"
|
|
.\" disable hyphenation
|
|
.nh
|
|
.\" disable justification (adjust text to left margin only)
|
|
.ad l
|
|
.SH "NAME"
|
|
dnssec\-keygen \- DNSSEC key generation tool
|
|
.SH "SYNOPSIS"
|
|
.HP 14
|
|
\fBdnssec\-keygen\fR {\-a\ \fIalgorithm\fR} {\-b\ \fIkeysize\fR} {\-n\ \fInametype\fR} [\fB\-c\ \fR\fB\fIclass\fR\fR] [\fB\-e\fR] [\fB\-f\ \fR\fB\fIflag\fR\fR] [\fB\-g\ \fR\fB\fIgenerator\fR\fR] [\fB\-h\fR] [\fB\-k\fR] [\fB\-p\ \fR\fB\fIprotocol\fR\fR] [\fB\-r\ \fR\fB\fIrandomdev\fR\fR] [\fB\-s\ \fR\fB\fIstrength\fR\fR] [\fB\-t\ \fR\fB\fItype\fR\fR] [\fB\-v\ \fR\fB\fIlevel\fR\fR] {name}
|
|
.SH "DESCRIPTION"
|
|
.PP
|
|
\fBdnssec\-keygen\fR
|
|
generates keys for DNSSEC (Secure DNS), as defined in RFC 2535 and RFC 4034. It can also generate keys for use with TSIG (Transaction Signatures), as defined in RFC 2845.
|
|
.PP
|
|
The
|
|
\fBname\fR
|
|
of the key is specified on the command line. For DNSSEC keys, this must match the name of the zone for which the key is being generated.
|
|
.SH "OPTIONS"
|
|
.PP
|
|
\-a \fIalgorithm\fR
|
|
.RS 4
|
|
Selects the cryptographic algorithm. For DNSSEC keys, the value of
|
|
\fBalgorithm\fR
|
|
must be one of RSAMD5, RSASHA1, DSA, NSEC3RSASHA1, NSEC3DSA, RSASHA256 or RSASHA512. For TSIG/TKEY, the value must be DH (Diffie Hellman), HMAC\-MD5, HMAC\-SHA1, HMAC\-SHA224, HMAC\-SHA256, HMAC\-SHA384, or HMAC\-SHA512. These values are case insensitive.
|
|
.sp
|
|
Note 1: that for DNSSEC, RSASHA1 is a mandatory to implement algorithm, and DSA is recommended. For TSIG, HMAC\-MD5 is mandatory.
|
|
.sp
|
|
Note 2: HMAC\-MD5 and DH automatically set the \-k flag.
|
|
.RE
|
|
.PP
|
|
\-b \fIkeysize\fR
|
|
.RS 4
|
|
Specifies the number of bits in the key. The choice of key size depends on the algorithm used. RSA keys must be between 512 and 2048 bits. Diffie Hellman keys must be between 128 and 4096 bits. DSA keys must be between 512 and 1024 bits and an exact multiple of 64. HMAC keys must be between 1 and 512 bits.
|
|
.RE
|
|
.PP
|
|
\-n \fInametype\fR
|
|
.RS 4
|
|
Specifies the owner type of the key. The value of
|
|
\fBnametype\fR
|
|
must either be ZONE (for a DNSSEC zone key (KEY/DNSKEY)), HOST or ENTITY (for a key associated with a host (KEY)), USER (for a key associated with a user(KEY)) or OTHER (DNSKEY). These values are case insensitive. Defaults to ZONE for DNSKEY generation.
|
|
.RE
|
|
.PP
|
|
\-c \fIclass\fR
|
|
.RS 4
|
|
Indicates that the DNS record containing the key should have the specified class. If not specified, class IN is used.
|
|
.RE
|
|
.PP
|
|
\-e
|
|
.RS 4
|
|
If generating an RSAMD5/RSASHA1 key, use a large exponent.
|
|
.RE
|
|
.PP
|
|
\-f \fIflag\fR
|
|
.RS 4
|
|
Set the specified flag in the flag field of the KEY/DNSKEY record. The only recognized flag is KSK (Key Signing Key) DNSKEY.
|
|
.RE
|
|
.PP
|
|
\-g \fIgenerator\fR
|
|
.RS 4
|
|
If generating a Diffie Hellman key, use this generator. Allowed values are 2 and 5. If no generator is specified, a known prime from RFC 2539 will be used if possible; otherwise the default is 2.
|
|
.RE
|
|
.PP
|
|
\-h
|
|
.RS 4
|
|
Prints a short summary of the options and arguments to
|
|
\fBdnssec\-keygen\fR.
|
|
.RE
|
|
.PP
|
|
\-k
|
|
.RS 4
|
|
Generate KEY records rather than DNSKEY records.
|
|
.RE
|
|
.PP
|
|
\-p \fIprotocol\fR
|
|
.RS 4
|
|
Sets the protocol value for the generated 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.
|
|
.RE
|
|
.PP
|
|
\-r \fIrandomdev\fR
|
|
.RS 4
|
|
Specifies the source of randomness. If the operating system does not provide a
|
|
\fI/dev/random\fR
|
|
or equivalent device, the default source of randomness is keyboard input.
|
|
\fIrandomdev\fR
|
|
specifies the name of a character device or file containing random data to be used instead of the default. The special value
|
|
\fIkeyboard\fR
|
|
indicates that keyboard input should be used.
|
|
.RE
|
|
.PP
|
|
\-s \fIstrength\fR
|
|
.RS 4
|
|
Specifies the strength value of the key. The strength is a number between 0 and 15, and currently has no defined purpose in DNSSEC.
|
|
.RE
|
|
.PP
|
|
\-t \fItype\fR
|
|
.RS 4
|
|
Indicates the use of the key.
|
|
\fBtype\fR
|
|
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.
|
|
.RE
|
|
.PP
|
|
\-v \fIlevel\fR
|
|
.RS 4
|
|
Sets the debugging level.
|
|
.RE
|
|
.SH "GENERATED KEYS"
|
|
.PP
|
|
When
|
|
\fBdnssec\-keygen\fR
|
|
completes successfully, it prints a string of the form
|
|
\fIKnnnn.+aaa+iiiii\fR
|
|
to the standard output. This is an identification string for the key it has generated.
|
|
.TP 4
|
|
\(bu
|
|
\fInnnn\fR
|
|
is the key name.
|
|
.TP 4
|
|
\(bu
|
|
\fIaaa\fR
|
|
is the numeric representation of the algorithm.
|
|
.TP 4
|
|
\(bu
|
|
\fIiiiii\fR
|
|
is the key identifier (or footprint).
|
|
.PP
|
|
\fBdnssec\-keygen\fR
|
|
creates two files, with names based on the printed string.
|
|
\fIKnnnn.+aaa+iiiii.key\fR
|
|
contains the public key, and
|
|
\fIKnnnn.+aaa+iiiii.private\fR
|
|
contains the private key.
|
|
.PP
|
|
The
|
|
\fI.key\fR
|
|
file contains a DNS KEY record that can be inserted into a zone file (directly or with a $INCLUDE statement).
|
|
.PP
|
|
The
|
|
\fI.private\fR
|
|
file contains algorithm\-specific fields. For obvious security reasons, this file does not have general read permission.
|
|
.PP
|
|
Both
|
|
\fI.key\fR
|
|
and
|
|
\fI.private\fR
|
|
files are generated for symmetric encryption algorithms such as HMAC\-MD5, even though the public and private key are equivalent.
|
|
.SH "EXAMPLE"
|
|
.PP
|
|
To generate a 768\-bit DSA key for the domain
|
|
\fBexample.com\fR, the following command would be issued:
|
|
.PP
|
|
\fBdnssec\-keygen \-a DSA \-b 768 \-n ZONE example.com\fR
|
|
.PP
|
|
The command would print a string of the form:
|
|
.PP
|
|
\fBKexample.com.+003+26160\fR
|
|
.PP
|
|
In this example,
|
|
\fBdnssec\-keygen\fR
|
|
creates the files
|
|
\fIKexample.com.+003+26160.key\fR
|
|
and
|
|
\fIKexample.com.+003+26160.private\fR.
|
|
.SH "SEE ALSO"
|
|
.PP
|
|
\fBdnssec\-signzone\fR(8),
|
|
BIND 9 Administrator Reference Manual,
|
|
RFC 2539,
|
|
RFC 2845,
|
|
RFC 4034.
|
|
.SH "AUTHOR"
|
|
.PP
|
|
Internet Systems Consortium
|
|
.SH "COPYRIGHT"
|
|
Copyright \(co 2004, 2005, 2007\-2010 Internet Systems Consortium, Inc. ("ISC")
|
|
.br
|
|
Copyright \(co 2000\-2003 Internet Software Consortium.
|
|
.br
|