From: Luca Ceresoli via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd.kuhls@t-online.de>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/exim: ignore CVE-2022-30333
Date: Mon, 1 Aug 2022 09:27:54 +0200 [thread overview]
Message-ID: <20220801092755.101dcb5d@booty> (raw)
In-Reply-To: <20220731112746.92822-1-bernd.kuhls@t-online.de>
Hi Bernd,
On Sun, 31 Jul 2022 13:27:46 +0200
Bernd Kuhls <bernd.kuhls@t-online.de> wrote:
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> package/exim/exim.mk | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/package/exim/exim.mk b/package/exim/exim.mk
> index e0fcd83fb0..a54a39c815 100644
> --- a/package/exim/exim.mk
> +++ b/package/exim/exim.mk
> @@ -10,6 +10,8 @@ EXIM_SITE = https://ftp.exim.org/pub/exim/exim4
> EXIM_LICENSE = GPL-2.0+
> EXIM_LICENSE_FILES = LICENCE
> EXIM_CPE_ID_VENDOR = exim
> +# fixed in version 4.94.2
> +EXIM_IGNORE_CVES += CVE-2022-30333
This CVE does not seem related to exim but rather to rarlab. Can you
either clarify what's going on or send a patch against rarlab?
Thank you!
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-08-01 7:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-31 11:27 [Buildroot] [PATCH 1/1] package/exim: ignore CVE-2022-30333 Bernd Kuhls
2022-08-01 7:27 ` Luca Ceresoli via buildroot [this message]
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=20220801092755.101dcb5d@booty \
--to=buildroot@buildroot.org \
--cc=bernd.kuhls@t-online.de \
--cc=luca.ceresoli@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