danetool(1) | User Commands | danetool(1) |
danetool - GnuTLS DANE tool
danetool [-flags] [-flag [value]] [--option-name[[=| ]value]]
All arguments must be options.
Tool to generate and check DNS resource records for the DANE protocol.
in the range 0 through 9999
Specifies the debug level.
This can be either a file or a PKCS #11 URL
This can be either a file or a PKCS #11 URL
This sets a DLV file to be used for DNSSEC verification.
Available hash functions are SHA1, RMD160, SHA256, SHA384, SHA512.
Obtains the DANE TLSA entry from the given hostname and prints information. Note that the actual certificate of the host can be provided using --load-certificate, otherwise danetool will connect to the server to obtain it. The exit code on verification success will be zero.
Checks the end-entity's certificate only. Trust anchors or CAs are not considered.
Checks the trust anchor's and CA's certificate only. End-entities are not considered.
This command prints the DANE RR data needed to enable DANE on a DNS server.
This command sets the hostname for the DANE RR.
This command specifies the protocol for the service set in the DANE data.
When the server's certificate isn't provided danetool will connect to the server to obtain the certificate. In that case it is required to know the protocol to talk with the server prior to initiating the TLS handshake.
Marks the DANE RR as a CA certificate if specified.
This option forces the generated record to contain the hash of the full X.509 certificate. By default only the hash of the public key is used.
DANE distinguishes certificates and public keys offered via the DNSSEC to trusted and local entities. This flag indicates that this is a domain-issued certificate, meaning that there could be no CA involved.
This option will use the local DNS server for DNSSEC. This is disabled by default due to many servers not allowing DNSSEC.
Ignores any DNSSEC signature verification results.
The input files will be assumed to be in DER or RAW format. Unlike options that in PEM input would allow multiple input data (e.g. multiple certificates), when reading in DER format a single data structure is read.
This option will print the received DANE data.
In that case on the exit code can be used as an indication of verification success
DANE TLSA RR generation
To create a DANE TLSA resource record for a certificate (or public
key) that was issued localy and may or may not be signed by a CA use the
following command.
$ danetool --tlsa-rr --host www.example.com --load-certificate cert.pem
To create a DANE TLSA resource record for a CA signed certificate,
which will be marked as such use the following command.
$ danetool --tlsa-rr --host www.example.com --load-certificate cert.pem --no-domain
The former is useful to add in your DNS entry even if your certificate is signed by a CA. That way even users who do not trust your CA will be able to verify your certificate using DANE.
In order to create a record for the CA signer of your certificate
use the following.
$ danetool --tlsa-rr --host www.example.com --load-certificate cert.pem --ca --no-domain
To read a server's DANE TLSA entry, use:
$ danetool --check www.example.com --proto tcp --port 443
To verify an HTTPS server's DANE TLSA entry, use:
$ danetool --check www.example.com --proto tcp --port 443 --load-certificate chain.pem
To verify an SMTP server's DANE TLSA entry, use:
$ danetool --check www.example.com --proto tcp --starttls-proto=smtp --load-certificate chain.pem
One of the following exit values will be returned:
certtool (1)
Copyright (C) 2020-2021 Free Software Foundation, and others all rights reserved. This program is released under the terms of the GNU General Public License, version 3 or later
Please send bug reports to: bugs@gnutls.org
09 Feb 2023 | 3.7.9 |