From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 86e9d04bfb73eb256682a567e187fe1e5cdcc3ca
Date: Fri, 25 Nov 2016 17:47:47 +0000 [thread overview]
Message-ID: <20161125174747.E087D1078E80@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1920 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via 86e9d04bfb73eb256682a567e187fe1e5cdcc3ca (commit)
from bc4a68812bb131be6a8413f69909bf6a3d5a89a2 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 86e9d04bfb73eb256682a567e187fe1e5cdcc3ca
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Fri Nov 25 17:45:39 2016 +0000
unbound: Deactivate qname-minimization & harden-below-nxdomain
This causes trouble when you try to resolve a record like
a.b.blah.com where b.blah.com responds with NXDOMAIN. unbound
won't try to resolve a.b.blah.com because it is assumed that
everything longer than b.blah.com does not exist which is
probably not good usability.
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/unbound/unbound.conf | 2 --
1 file changed, 2 deletions(-)
Difference in files:
diff --git a/config/unbound/unbound.conf b/config/unbound/unbound.conf
index 3f724d8..c9b01b8 100644
--- a/config/unbound/unbound.conf
+++ b/config/unbound/unbound.conf
@@ -42,7 +42,6 @@ server:
# Privacy Options
hide-identity: yes
hide-version: yes
- qname-minimisation: yes
minimal-responses: yes
# DNSSEC
@@ -56,7 +55,6 @@ server:
harden-short-bufsize: no
harden-large-queries: yes
harden-dnssec-stripped: yes
- harden-below-nxdomain: yes
harden-referral-path: yes
harden-algo-downgrade: no
use-caps-for-id: no
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2016-11-25 17:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20161125174747.E087D1078E80@git01.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@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