From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 2/3] Unbound: Use caps for IDs
Date: Thu, 23 Aug 2018 14:40:42 +0100 [thread overview]
Message-ID: <d3fcd3426230ecae1b1df91c97b7309dc8f92996.camel@ipfire.org> (raw)
In-Reply-To: <c9d3419f-5ca9-bcfa-9e01-7047025af279@link38.eu>
[-- Attachment #1: Type: text/plain, Size: 1195 bytes --]
This was deliberately not enabled because the documentation contains a
warning about various incompatibilities with various other DNS servers.
Is there some sort of study saying that this can be safely enabled?
-Michael
On Sun, 2018-08-19 at 20:11 +0200, Peter Müller wrote:
> Attempt to detect DNS spoofing attacks by inserting 0x20-encoded
> random bits into upstream queries. Upstream documentation claims
> it to be an experimental implementation, it did not cause any trouble
> on productive systems here.
>
> See https://nlnetlabs.nl/documentation/unbound/unbound.conf/ for
> further details.
>
> Signed-off-by: Peter Müller <peter.mueller(a)link38.eu>
> ---
> config/unbound/unbound.conf | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/config/unbound/unbound.conf b/config/unbound/unbound.conf
> index fa2ca3fd4..8b5d34ee3 100644
> --- a/config/unbound/unbound.conf
> +++ b/config/unbound/unbound.conf
> @@ -59,7 +59,7 @@ server:
> harden-below-nxdomain: yes
> harden-referral-path: yes
> harden-algo-downgrade: no
> - use-caps-for-id: no
> + use-caps-for-id: yes
>
> # Harden against DNS cache poisoning
> unwanted-reply-threshold: 5000000
next prev parent reply other threads:[~2018-08-23 13:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-19 18:11 Peter Müller
2018-08-23 13:40 ` Michael Tremer [this message]
2018-08-23 19:15 ` Peter Müller
2018-08-24 11:51 ` Michael Tremer
2018-08-27 15:26 ` [PATCH 2/3 v2] " Peter Müller
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=d3fcd3426230ecae1b1df91c97b7309dc8f92996.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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