From: James Cloos <cloos@jhcloos.com>
To: Alon Bar-Lev <alonbl@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] bugs.gentoo.org and dnssec
Date: Tue, 21 Apr 2015 13:40:34 -0400 [thread overview]
Message-ID: <m3pp6xwfal.fsf@carbon.jhcloos.org> (raw)
In-Reply-To: <CAOazyz3fwV4hmO3ZAKuSZ9fdFPdBjF6u2R286KkxVJihfXWZ3A@mail.gmail.com> (Alon Bar-Lev's message of "Tue, 21 Apr 2015 20:27:27 +0300")
>>>>> "AB" == Alon Bar-Lev <alonbl@gentoo.org> writes:
AB> When using bugs.gentoo.org with dnsmasq and dnssec enabled, I cannot
AB> access attachments.
It works here using a local unbound.
But dnsmasq had some growth pains when it added dnssec verification, due
to its bottom-up rather than the ususal top-down approach.
AIUI, the current release should work.
If you see that issue with 2.72 or later, they'd like to hear about it.
Their list is: dnsmasq-discuss@lists.thekelleys.org.uk
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 0x997A9F17ED7DAEA6
next prev parent reply other threads:[~2015-04-21 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 17:27 [gentoo-dev] bugs.gentoo.org and dnssec Alon Bar-Lev
2015-04-21 17:40 ` James Cloos [this message]
2015-04-21 17:51 ` Alon Bar-Lev
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=m3pp6xwfal.fsf@carbon.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=alonbl@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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