☰

如何为 certbot 插件“certbot-dns-rfc2136”生成 TSIG 密钥

tag-icon • tag-icon bind9
如何为 certbot 插件“certbot-dns-rfc2136”生成 TSIG 密钥

我正在配置 BIND9 以获取通配符证书让我们加密。当我尝试根据以下内容生成 TSIG 密钥时此处说明，我收到以下错误：

# dnssec-keygen -a HMAC-SHA512 -b 512 -n HOST keyname.
dnssec-keygen: fatal: unknown algorithm HMAC-SHA512

然后我阅读帮助并文档关于dnssec-keygen，没有称为的算法HMAC-SHA512的确：

# dnssec-keygen -h
Usage:
    dnssec-keygen [options] name

Version: 9.14.2
    name: owner of the key
Options:
    -K <directory>: write keys into directory
    -a <algorithm>:
        RSASHA1 | NSEC3RSASHA1 |
        RSASHA256 | RSASHA512 |
        ECDSAP256SHA256 | ECDSAP384SHA384 |
        ED25519 | ED448 | DH
    -3: use NSEC3-capable algorithm
    -b <key size in bits>:
        RSASHA1:        [1024..4096]
        NSEC3RSASHA1:   [1024..4096]
        RSASHA256:      [1024..4096]
        RSASHA512:      [1024..4096]
        DH:             [128..4096]
        ECDSAP256SHA256:        ignored
        ECDSAP384SHA384:        ignored
        ED25519:        ignored
        ED448:  ignored
        (key size defaults are set according to
        algorithm and usage (ZSK or KSK)
    -n <nametype>: ZONE | HOST | ENTITY | USER | OTHER
        (DNSKEY generation defaults to ZONE)
    -c <class>: (default: IN)
    -d <digest bits> (0 => max, default)
    -E <engine>:
        name of an OpenSSL engine to use
    -f <keyflag>: KSK | REVOKE
    -g <generator>: use specified generator (DH only)
    -L <ttl>: default key TTL
    -p <protocol>: (default: 3 [dnssec])
    -s <strength>: strength value this key signs DNS records with (default: 0)
    -T <rrtype>: DNSKEY | KEY (default: DNSKEY; use KEY for SIG(0))
    -t <type>: AUTHCONF | NOAUTHCONF | NOAUTH | NOCONF (default: AUTHCONF)
    -h: print usage and exit
    -m <memory debugging mode>:
       usage | trace | record | size | mctx
    -v <level>: set verbosity level (0 - 10)
    -V: print version information
Timing options:
    -P date/[+-]offset/none: set key publication date (default: now)
    -P sync date/[+-]offset/none: set CDS and CDNSKEY publication date
    -A date/[+-]offset/none: set key activation date (default: now)
    -R date/[+-]offset/none: set key revocation date
    -I date/[+-]offset/none: set key inactivation date
    -D date/[+-]offset/none: set key deletion date
    -D sync date/[+-]offset/none: set CDS and CDNSKEY deletion date
    -G: generate key only; do not set -P or -A
    -C: generate a backward-compatible key, omitting all dates
    -S <key>: generate a successor to an existing key
    -i <interval>: prepublication interval for successor key (default: 30 days)
Output:
     K<name>+<alg>+<id>.key, K<name>+<alg>+<id>.private

我深入研究另一个问题：无法通过 dnssec-keygen 生成密钥，但我的问题仍然没有解决。

我应该怎么办？

答案1

经过一番搜索，我发现插件的文档certbot-dns-rfc2136是过时的！

在BIND9的官方git存储库中，我发现了以下内容提交消息:

  1. [func] 不推荐使用 dnssec-keygen 生成 HMAC 密钥，转而使用 tsig-keygen。用于此目的时，dnssec-keygen 将打印警告。在未来版本中，所有 HMAC 算法都将从 dnssec-keygen 中删除。 [RT#42272]

所以，最终的解决方案是：

tsig-keygen -a hmac-sha512 tsig-key > /etc/bind/tsig.key

相关内容