From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Chris Packham <judge.packham@gmail.com>
Cc: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/2] syslog-ng: bump version to 4.3.1
Date: Mon, 11 Sep 2023 21:40:51 +0200 [thread overview]
Message-ID: <20230911214051.0da8179c@windsurf> (raw)
In-Reply-To: <20230911155225.0a63879f@windsurf>
Hello Chris,
On Mon, 11 Sep 2023 15:52:25 +0200
Thomas Petazzoni via buildroot <buildroot@buildroot.org> wrote:
> On Mon, 11 Sep 2023 20:49:59 +1200
> Chris Packham <judge.packham@gmail.com> wrote:
>
> > Update to latest version. This includes a fix for CVE-2022-38725.
>
> So this is a security bump?
Actually, are you sure it is related to CVE-2022-38725. According to
https://nvd.nist.gov/vuln/detail/CVE-2022-38725, this CVE only affects
versions up to 3.38, and we're at 4.2.0. In addition,
https://github.com/syslog-ng/syslog-ng/releases/tag/syslog-ng-4.3.1
does not mention "CVE" anywhere. Could you clarify this?
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:[~2023-09-11 19:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 8:49 [Buildroot] [PATCH 1/2] syslog-ng: bump version to 4.3.1 Chris Packham
2023-09-11 8:50 ` [Buildroot] [PATCH 2/2] gst1-shark: Update to v0.8.1 Chris Packham
2023-09-11 19:42 ` Thomas Petazzoni via buildroot
2023-09-11 13:52 ` [Buildroot] [PATCH 1/2] syslog-ng: bump version to 4.3.1 Thomas Petazzoni via buildroot
2023-09-11 19:40 ` Thomas Petazzoni via buildroot [this message]
2023-09-11 19:45 ` Chris Packham
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=20230911214051.0da8179c@windsurf \
--to=buildroot@buildroot.org \
--cc=judge.packham@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 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.