keymgr – Key management utility¶
Synopsis¶
keymgr basic_option [parameters...]
keymgr [config_option config_storage] zone command argument...
Description¶
The keymgr utility serves for manual key management in Knot DNS server.
Functions for DNSSEC keys and KASP (Key And Signature Policy) management are provided.
The DNSSEC and KASP configuration is stored in a so called KASP database. The database is backed by LMDB.
Basic options¶
- -h, –help
- Print the program help.
- -V, –version
- Print the program version.
- -t tsig_name [tsig_algorithm] [tsig_bits]
- Generates TSIG key. TSIG algorithm can be specified by string (default: hmac-sha256), bit length of the key by number (default: optimal length given by algorithm).
Config options¶
- -c
- Use specified Knot DNS configuration file path.
- -C
- Use specified Knot DNS configuration database path. The default configuration database, if exists, has a preference to the default configuration file.
- -d
- Use specified KASP database path and default configuration.
Commands¶
- list
- Prints the list of key IDs and parameters of keys belonging to the zone.
- generate [arguments...]
- Generates new DNSSEC key and stores it in KASP database. Prints the key ID. This action takes some number of arguments (see below). Values for unspecified arguments are taken from corresponding policy (if -c or -C options used) or from Knot policy defaults.
- import-bind BIND_key_file
- Imports a BIND-style key into KASP database (converting it to PEM format). Takes one argument: path to BIND key file (private or public, but both MUST exist).
- import-pem PEM_file [arguments...]
- Imports a DNSSEC key from PEM file. The key parameters (same as for the generate action) need to be specified (mainly algorithm, timers...) because they are not contained in the PEM format.
- set key_spec [arguments...]
- Changes a timing argument of an existing key to a new timestamp. Key_spec is either the key tag or a prefix of the key ID; arguments are like for generate, but just the timing-related ones.
- ds [key_spec]
- Generate DS record (all digest algorithms together) for specified key. Key_spec is like for set, if unspecified, all KSKs are used.
- dnskey [key_spec]
- Generate DNSKEY record for specified key. Key_spec is like for ds, if unspecified, all KSKs are used.
- delete key_spec
- Remove the specified key from zone. If the key was not shared, it is also deleted from keystore.
- share key_ID
- Import a key (specified by full key ID) from another zone as shared. After this, the key is owned by both zones equally.
Generate arguments¶
Arguments are separated by space, each of them is in format ‘name=value’.
- algorithm
- Either an algorithm number (e.g. 14), or text name without dashes (e.g. ECDSAP384SHA384).
- size
- Key length in bits.
- ksk
- Either ‘true’ (KSK will be generated) or ‘false’ (ZSK will be generated).
- created
- Timestamp of key creation.
- publish
- Timestamp for key to be published.
- ready
- Timestamp for key to be pre-activated and submitted (in case of KSK).
- active
- Timestamp for key to be activated.
- retire
- Timestamp for key to be de-activated.
- remove
- Timestamp for key ot be deleted.
Timestamps¶
- 0
- Zero timestamp means infinite future.
- UNIX_time
- Positive number of seconds since 1970.
- YYYYMMDDHHMMSS
- Date and time in this format without any punctuation.
- relative_timestamp
- The word “now” followed by sign (+, -), a number and a shortcut for time unit (y, mo, d, h, mi, (nothing = seconds)), e.g. now+1mi, now-2mo, now+10, now+0, now-1y, ...
Examples¶
Generate new TSIG key:
$ keymgr -t my_name hmac-sha384Generate new DNSSEC key:
$ keymgr example.com. generate algorithm=ECDSAP256SHA256 size=256 \ ksk=true created=1488034625 publish=20170223205611 retire=now+10mo remove=now+1y
Import a DNSSEC key from BIND:
$ keymgr example.com. import-bind ~/bind/Kharbinge4d5.+007+63089.keyConfigure key timing:
$ keymgr example.com. set 4208 active=now+2mi retire=now+4mi remove=now+5mi
Share a KSK from another zone:
$ keymgr example.com. share e687cf927029e9db7184d2ece6d663f5d1e5b0e9
