From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: 52377-done@debbugs.gnu.org, guix-patches@gnu.org
Subject: bug#52377: [security 1/2] gnu: BIND: Update to 9.16.23 [fixes CVE-2021-{25218, 25219}].
Date: Thu, 09 Dec 2021 01:29:17 +0100 [thread overview]
Message-ID: <87fsr2vcif.fsf@nckx> (raw)
In-Reply-To: <58bbbfdf122385ca92de71aaa5bbe7a113ec0980.1638993806.git.leo@famulari.name>
[-- Attachment #1: Type: text/plain, Size: 747 bytes --]
Leo,
Leo Famulari 写道:
> * gnu/packages/dns.scm (isc-bind): Update to 9.16.23.
Thanks!
I updated BIND to 9.16.23 in commit
4ca0e9d5f77ec309a5a8a7eba3d97fd3bb4852d5, which reverts the
upstream commit that caused this new test failure. I had to
tediously bisect this; I never would've guessed it was to blame.
The patch won't keep forever. Bug reports to ISC seem to require
a GitLab account. Can't say I'm in a terrible rush to create yet
another one. Do you have one?
Maybe this problem will just go away with a newer GCC. We can
hope…
I went ahead and pushed your matching isc-dhcp patch. I wouldn't
normally do this to people with commit access but it seemed
justified.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2021-12-09 0:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 19:56 [bug#52377] [security]: Update BIND DNS Leo Famulari
2021-12-08 20:03 ` [bug#52377] [security 1/2] gnu: BIND: Update to 9.16.23 [fixes CVE-2021-{25218, 25219}] Leo Famulari
2021-12-08 20:03 ` [bug#52377] [security 2/2] gnu: isc-dhcp: Update bundled BIND to 9.11.36 [fixes CVE-2021-25219] Leo Famulari
2021-12-08 20:12 ` [bug#52377] [security 1/2] gnu: BIND: Update to 9.16.23 [fixes CVE-2021-{25218, 25219}] Leo Famulari
2021-12-08 20:35 ` Leo Famulari
2021-12-09 0:29 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2021-12-09 4:14 ` Leo Famulari
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=87fsr2vcif.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=52377-done@debbugs.gnu.org \
--cc=leo@famulari.name \
--cc=me@tobias.gr \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.