From: "ito-yuichi@fujitsu.com" <ito-yuichi@fujitsu.com>
To: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] [PATCH] cyrus-sasl: add CVE-2020-8032 to allowlist
Date: Thu, 17 Jun 2021 04:10:06 +0000 [thread overview]
Message-ID: <TYCPR01MB5599FD7F21812AFB694953FF8F0E9@TYCPR01MB5599.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <16877A0991CEE112.8333@lists.openembedded.org>
Hi,
I would appreciate if you have any advice on this patch.
> -----Original Message-----
> From: openembedded-devel@lists.openembedded.org
> <openembedded-devel@lists.openembedded.org> On Behalf Of
> ito-yuichi@fujitsu.com
> Sent: Friday, June 11, 2021 5:33 PM
> To: openembedded-devel@lists.openembedded.org
> Subject: [oe] [PATCH] cyrus-sasl: add CVE-2020-8032 to allowlist
>
> This affects only openSUSE, so add it to allowlist.
>
> Signed-off-by: Yuichi Ito <ito-yuichi@fujitsu.com>
> ---
> .../recipes-daemons/cyrus-sasl/cyrus-sasl_2.1.27.bb | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git
> a/meta-networking/recipes-daemons/cyrus-sasl/cyrus-sasl_2.1.27.bb
> b/meta-networking/recipes-daemons/cyrus-sasl/cyrus-sasl_2.1.27.bb
> index 33de8ca7e..c4b41ace8 100644
> --- a/meta-networking/recipes-daemons/cyrus-sasl/cyrus-sasl_2.1.27.bb
> +++ b/meta-networking/recipes-daemons/cyrus-sasl/cyrus-sasl_2.1.27.bb
> @@ -96,3 +96,6 @@ FILES_${PN}-dbg += "${libdir}/sasl2/.debug"
> FILES_${PN}-staticdev += "${libdir}/sasl2/*.a"
>
> INSANE_SKIP_${PN} += "dev-so"
> +
> +# CVE-2020-8032 affects only openSUSE
> +CVE_CHECK_WHITELIST += "CVE-2020-8032"
> --
> 2.25.1
next parent reply other threads:[~2021-06-17 4:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16877A0991CEE112.8333@lists.openembedded.org>
2021-06-17 4:10 ` ito-yuichi [this message]
2021-06-17 5:38 ` [oe] [PATCH] cyrus-sasl: add CVE-2020-8032 to allowlist Khem Raj
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=TYCPR01MB5599FD7F21812AFB694953FF8F0E9@TYCPR01MB5599.jpnprd01.prod.outlook.com \
--to=ito-yuichi@fujitsu.com \
--cc=openembedded-devel@lists.openembedded.org \
/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.