From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/bind: security bump version to 9.20.17
Date: Tue, 3 Feb 2026 11:41:24 +0100 [thread overview]
Message-ID: <aYHQjwF-IrYqiszL@windsurf> (raw)
In-Reply-To: <20260104172232.3437646-1-giulio.benetti@benettiengineering.com>
Hello,
On Sun, Jan 04, 2026 at 06:22:25PM +0100, Giulio Benetti wrote:
> Release notes:
> https://ftp.isc.org/isc/bind9/9.20.17/doc/arm/html/notes.html
>
> Changelog:
> https://ftp.isc.org/isc/bind9/9.20.17/doc/arm/html/changelog.html
>
> No new CVEs fixed compared to version 9.18.41.
I'm confused: your title says it's a security bump, but your commit
message says there are "no new CVEs fixed compared to version 9.18.41"
(which is the version that we have in Buildroot right now).
So is this a security bump, or not?
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-02-03 10:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-04 17:22 [Buildroot] [PATCH] package/bind: security bump version to 9.20.17 Giulio Benetti
2026-01-04 17:22 ` [Buildroot] [PATCH] DEVELOPERS: add Giulio Benetti to package bind Giulio Benetti
2026-02-03 10:42 ` Thomas Petazzoni via buildroot
2026-02-13 19:37 ` Thomas Perale via buildroot
2026-02-03 10:41 ` Thomas Petazzoni via buildroot [this message]
2026-02-03 11:07 ` [Buildroot] [PATCH] package/bind: security bump version to 9.20.17 Giulio Benetti
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=aYHQjwF-IrYqiszL@windsurf \
--to=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=thomas.petazzoni@bootlin.com \
/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