From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Florian Weimer <fweimer@redhat.com>, linux-man@vger.kernel.org
Cc: mtk.manpages@gmail.com
Subject: Re: [PATCH] resolv.5: Document the trust-ad option
Date: Mon, 12 Oct 2020 20:55:48 +0200 [thread overview]
Message-ID: <b2f05cdb-8316-4a14-c64f-7f63d3bda3c2@gmail.com> (raw)
In-Reply-To: <87sgaj1yfe.fsf@oldenburg2.str.redhat.com>
On 10/12/20 1:22 PM, Florian Weimer wrote:
> Signed-off-by: Florian Weimer <fweimer@redhat.com>
Thanks, Florian. Patch applied.
Cheers
Michael
> ---
> man5/resolv.conf.5 | 31 ++++++++++++++++++++++++++++---
> 1 file changed, 28 insertions(+), 3 deletions(-)
>
> diff --git a/man5/resolv.conf.5 b/man5/resolv.conf.5
> index 7013c8a28..6f3de7faf 100644
> --- a/man5/resolv.conf.5
> +++ b/man5/resolv.conf.5
> @@ -35,9 +35,10 @@ The resolver configuration file contains information that is read
> by the resolver routines the first time they are invoked by a process.
> The file is designed to be human readable and contains a list of
> keywords with values that provide various types of resolver information.
> -The configuration file is considered a trusted source of DNS information
> -(e.g., DNSSEC AD-bit information will be returned unmodified from this
> -source).
> +The configuration file is considered a trusted source of DNS information;
> +see the
> +.B trust-ad
> +option below for details.
> .PP
> If this file does not exist, only the name server on the local machine
> will be queried, and the search list contains the local domain name
> @@ -317,6 +318,30 @@ Sets
> in
> .IR _res.options .
> This option disables automatic reloading of a changed configuration file.
> +.TP
> +.BR trust\-ad " (since glibc 2.31)"
> +.\" 446997ff1433d33452b81dfa9e626b8dccf101a4
> +Sets
> +.BR RES_TRUSTAD
> +in
> +.IR _res.options .
> +This option controls the AD bit behavior of the stub resolver. If a
> +validating resolver sets the AD bit in a response, it indicates that
> +the data in the response was verified according to the DNSSEC
> +protocol. In order to rely on the AD bit, the local system has to
> +trust both the DNSSEC-validating resolver and the network path to it,
> +which is why an explicit opt-in is required. If the
> +.B trust\-ad
> +option is active, the stub resolver sets the AD bit in outgoing DNS
> +queries (to enable AD bit support), and preserves the AD bit in
> +responses. Without this option, the AD bit is not set in queries, and
> +it is always removed from responses before they are returned to the
> +application. This means that applications can trust the AD bit in
> +responses if the
> +.B trust\-ad
> +option has been set correctly. In glibc version 2.30 and earlier, the
> +AD is not set automatically in queries, and passed through unchanged
> +to applications in responses.
> .RE
> .PP
> The \fIsearch\fP keyword of a system's \fIresolv.conf\fP file can be
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2020-10-12 18:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 11:22 [PATCH] resolv.5: Document the trust-ad option Florian Weimer
2020-10-12 18:55 ` Michael Kerrisk (man-pages) [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b2f05cdb-8316-4a14-c64f-7f63d3bda3c2@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=fweimer@redhat.com \
--cc=linux-man@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox