4.13. dnssec-keyfromlabel --- DNSKEY generator (HSM)¶
dnssec-keyfromlabel [-l label] [-a algorithm] [-A date/offset] [-c class] [-D date/offset] [-E <engine-name>] [-f flag] [-G] [-I date/offset] [-i interval] [-K directory] [-L <ttl>] [-n nametype] [-P date/offset] [-p protocol] [-R date/offset] [-S key] [-T <rrtype>] [-t type] [-v level] [-V] [-y] <name>
dnssec-keyfromlabel generates a key pair of files that referencing a key object stored in a cryptographic hardware service module (HSM). The private key file can be used for DNSSEC signing of zone data as if it were a conventional signing key created by dnssec-keygen(1), but the key material is stored within the HSM, and the actual signing takes place there.
Selects the cryptographic algorithm. For DNSSEC keys, the value of <algorithm> must be one of RSASHA1, NSEC3RSASHA1, RSASHA256, RSASHA512, ECDSAP256SHA256, ECDSAP384SHA384, ED25519 or ED448. For KEY keys, the value must be DH (Diffie Hellman). These values are case-insensitive.
If no algorithm is specified, then ECDSAP256SHA256 will be used by default.
DH automatically sets the
Specifies the OpenSSL engine to use for cryptographic operations, such as a secure key store used for signing.
Specifies the label for a key pair in the crypto hardware.
The label is an arbitrary string that identifies a particular key. It may be preceded by an optional OpenSSL engine name, followed by a colon, as in pkcs11:keylabel.
If the label contains a pin-source field, tools using the generated key files will be able to use the HSM for signing and other operations without any need for an operator to manually enter a PIN.
Making the HSM's PIN accessible in this manner may reduce the security advantage of using an HSM. Be sure this is what you want to do before making use of this feature.
Specifies the owner type of the key. The value of <name-type> 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.
Indicates that the DNS record containing the key should have the specified class. If not specified, class IN is used.
Print program usage information and exit.
Sets the directory in which the key files are to be written.
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. If this value is not set and there is no existing DNSKEY RRset, the TTL will default to the SOA TTL. Setting the default TTL to 0 or none is the same as leaving it unset.
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.
Create a new key as an explicit successor to an existing key. The name, algorithm, size, and type of the key will be set to match the existing key. The activation date of the new key will be set to the inactivation date of the existing one. The publication date will be set to the activation date minus the pre-publication interval, which defaults to 30 days.
Specifies the resource record type to use for the key. <rrtype> must be either DNSKEY or KEY. The default is DNSKEY when using a DNSSEC algorithm, but it can be overridden to KEY for use with SIG(0).
Using the DH algorithm forces this option to KEY.
Indicates the use of the key. <type> 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.
Set the verbosity level.
Print the program's version and exit.
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 not safe to use if you will be using RFC 5011 trust anchor maintenance with either of the keys involved.
The name of the key. This must match the name of the zone for which the key is being generated.
4.13.4. Timing options¶
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.
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
-Goption has not been used, the default is now.
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.)
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
-Goption has not been used, the default is now. If set, and if
-Pis not set, then the publication date will be set to the activation date minus the prepublication interval.
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.
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.
Sets the pre-publication interval for a key. If set, then the publication and activation dates must be separated by at least this much time. If the activation date is specified but the publication date isn't, then the publication date will default to this much time before the activation date; conversely, if the publication date is specified but activation date isn't, then activation will be set to this much time after publication.
If the key is being created as an explicit successor to another key, then the default prepublication interval is 30 days; otherwise it is zero.
As with date offsets, if the argument is followed by one of the suffixes y, mo, w, d, h, or mi, then the interval is measured in years, months, weeks, days, hours, or minutes, respectively. Without a suffix, the interval is measured in seconds.
4.13.5. Generated key files¶
When dnssec-keyfromlabel completes successfully, it prints a string of the form Knnnn.+aaa+iiiii to the standard output. This is an identification string for the key files it has generated.
<nnnn> is the key name.
<aaa> is the numeric representation of the algorithm.
<iiiii> is the key identifier (or footprint).
dnssec-keyfromlabel creates two files, with names based on the printed string. Knnnn.+aaa+iiiii.key contains the public key, and Knnnn.+aaa+iiiii.private contains the private key.
The .key file contains a DNSKEY record that can be inserted into a zone file (directly or with a $INCLUDE statement).
The .private file contains algorithm-specific fields. For obvious security reasons, this file does not have general read permission.
4.13.6. See also¶
Copyright (c) 2019-2020 Akira Systems Private Limited. All rights reserved.
Copyright (c) 2008-2012, 2014-2018 Internet Systems Consortium, Inc. ("ISC").