From: Thomas Deutschmann <whissi@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] net-dns/dnssec-root: Blind stable on arm, critical bug 667774
Date: Thu, 11 Oct 2018 19:14:00 +0200 [thread overview]
Message-ID: <95271f29-6c3c-1b9c-f12b-96c467b8bdec@gentoo.org> (raw)
In-Reply-To: <CAAr7Pr_RiRWAv=NTOxMSnpiRkWkPqp3c6iWmmNKjxf1xz7BqPg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1606 bytes --]
On 2018-10-11 17:48, Alec Warner wrote:
> This thread is missing a bunch of context...so I'll try to add it I guess.
All you need to know in this commit message, included linked bug report
for more details. :)
> I can't tell if the complaint is that:
>
> 1) Someone blind-stabled something on arm and it broke (doesn't build?)
> 2) The arm team failed to mark a package stable before a hard deadline
> (DNSSEC key rotation)
>
> I presume its the latter? Whats the impact? All DNS, or only DNSSEC
> validated entries?
It's the latter. It will affect anyone running an own DNS resolver like
net-dns/unbound on ARM with DNSSEC enabled (not default) using keys
provided by net-dns/dnssec-root package.
Of course anyone familiar with DNSSEC or unbound maybe knows how to
workaround:
- Enable auto-anchor update; However it is too late to do that know,
it will take ~30 days until the new learned key will become trusted.
Same applies to any *new* setup within last 30 days.
- Use unbound-anchor tool to force a manual immediate update.
- Disable DNSSEC validation.
But that's not the point here. The point was to get some attention that
again we have a lacking architecture (net-dns/dnssec-root is not the
only package where ARM arch team is lacking behind) which affects anyone
"trusting" somehow in STABLE keywords.
If everyone is using ~ARCH and don't care about STABLE keywords, well,
we could save a bunch of time, energy...
--
Regards,
Thomas Deutschmann / Gentoo Linux Developer
C4DD 695F A713 8F24 2AA1 5638 5849 7EE5 1D5D 74A5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next prev parent reply other threads:[~2018-10-11 17:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 15:10 [gentoo-dev] net-dns/dnssec-root: Blind stable on arm, critical bug 667774 Thomas Deutschmann
2018-10-11 15:45 ` Corentin “Nado” Pazdera
2018-10-11 17:04 ` Thomas Deutschmann
2018-10-11 17:07 ` Alec Warner
2018-10-11 18:07 ` Marc Schiffbauer
2018-10-11 15:48 ` Alec Warner
2018-10-11 17:14 ` Thomas Deutschmann [this message]
2018-10-12 10:07 ` Jeroen Roovers
2018-10-12 12:50 ` Rich Freeman
2018-10-20 12:19 ` Andreas Sturmlechner
2018-10-20 12:22 ` Mikle Kolyada
2018-10-20 12:26 ` Andreas Sturmlechner
2018-10-20 12:56 ` Mikle Kolyada
2018-10-20 13:29 ` Rich Freeman
2018-10-11 23:38 ` Sergei Trofimovich
2018-10-12 0:40 ` Thomas Deutschmann
2018-10-12 7:28 ` Sergei Trofimovich
2018-10-12 2:12 ` Matt Turner
2018-10-12 13:47 ` [gentoo-dev] " Mikle Kolyada
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=95271f29-6c3c-1b9c-f12b-96c467b8bdec@gentoo.org \
--to=whissi@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