From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/avahi: security bump to version 0.9-rc1
Date: Sat, 27 Jul 2024 16:15:47 +0200 [thread overview]
Message-ID: <20240727161547.3c7afc77@windsurf> (raw)
In-Reply-To: <20240727135252.389739-1-fontaine.fabrice@gmail.com>
Hello Fabrice,
On Sat, 27 Jul 2024 15:52:52 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> - Drop patch (already in version)
> - Fix CVE-2021-3468 and CVE-2023-38469 to CVE-2023-38473
> - --{en,dis}able-libsystemd must be passed since
> https://github.com/avahi/avahi/commit/bc116c05b15f1f478a40e47fe9fc68011cef1e50
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
I'm a bit uneasy with moving to a release candidate version. How much
effort is it to backport the CVE fixes onto version 0.8 ?
Alternatively, do we have some visibility on when the final 0.9 will be
released? Knowing that 0.8 dates back from 2020, it seems like the
project is not particularly quick at making new releases :-)
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:[~2024-07-27 14:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-27 13:52 [Buildroot] [PATCH 1/1] package/avahi: security bump to version 0.9-rc1 Fabrice Fontaine
2024-07-27 14:15 ` Thomas Petazzoni via buildroot [this message]
2024-07-27 14:24 ` Fabrice Fontaine
2024-08-02 6:37 ` Thomas Petazzoni via buildroot
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=20240727161547.3c7afc77@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.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