From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 2/3] Unbound: Use caps for IDs
Date: Fri, 24 Aug 2018 12:51:36 +0100 [thread overview]
Message-ID: <725e66c3c94bb11360bc41ab37bbd4b7f1485cbc.camel@ipfire.org> (raw)
In-Reply-To: <0af7be2f-4c01-4ac1-235f-8797de6822ff@link38.eu>
[-- Attachment #1: Type: text/plain, Size: 2646 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Okay, let's give it a try then.
On Thu, 2018-08-23 at 21:15 +0200, Peter Müller wrote:
> Hello,
>
> > This was deliberately not enabled because the documentation contains a
> > warning about various incompatibilities with various other DNS servers.
>
> Yes, there are a lot of broken DNS servers out there...
> >
> > Is there some sort of study saying that this can be safely enabled?
>
> I know people operating DNS resolvers for > 30k customers with this setting
> enabled. They never experienced any issue with this so far. This is enabled
> on my systems too.
>
> Currently, I am not aware of a public study.
>
> Best regards,
> Peter Müller
> >
> > -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
>
>
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE5/rW5l3GGe2ypktxgHnw/2+QCQcFAlt/8UgACgkQgHnw/2+Q
CQd1JBAAgbHWIFzbXOOcaiQHgzyi3gVeZ4tnV8sMx3Fm563dBU0f24BteOm6lYDl
nu9bqYIGsmIPBpc1Hweqjatc5bkU9NUH3YNCI5LSbu4a66r1wbHpFjpCZTwstufl
THO6BLsm2karfXezpxWi9U+Ug3E2KWMvBnnpdTWy4QfiOQXQttqVoeMOVKLwpaM0
5ExsdjNl7caneflXA3C2Igo1Om7H2+bWQ82TyCD8kjb/SBxuTVfFzACPmWVjUwt7
wmhZiBUpR5vDWkikv4j7AHmi2aT7SKkIGcQiOQvn+sMa/tAqys9B3H5kxXuQYBWs
DdqnIKVAOqk6EhxcDae6zthM+iKy5k5RCjxj6M4qUJXb14/b7LBecxZsiyI2rY1/
8LiUzlq5WnpH8Qkf4f8uV42JGMi4JoY+Tz3css3BWnOB/jN7muIXqTP2DaKv7/rE
weseImTTWftdIPtGlkg0ALMVuErHx0I5hmADfiYbjhJjSD8M9h0Ya7Mxlp5jXcvE
gCq2mrXJxltvJnoQm7GYoK+ivQp9mW/bF+vc0hF7DhtIdFP7lTh0nYQVDgkaMU4k
sAGGk+kovSqQIKuMcZYAjgw759aKVhEfJXNPMqUs7YcrN8lIq19a31vTToJLcEfW
bsopTQJhG9oAb+dWnjDMtICCxlnferRKTVvkbxoUIhe+Y2hYTZw=
=YbLO
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2018-08-24 11:51 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
2018-08-23 19:15 ` Peter Müller
2018-08-24 11:51 ` Michael Tremer [this message]
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=725e66c3c94bb11360bc41ab37bbd4b7f1485cbc.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