From: Randy MacLeod <randy.macleod@windriver.com>
To: soumya.sambu@windriver.com,
Richard Purdie <richard.purdie@linuxfoundation.org>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
"steve@sakoman.com" <steve@sakoman.com>
Cc: "Polampalli, Archana" <Archana.Polampalli@windriver.com>
Subject: Re: [OE-core] [PATCH] perl: fix CVE-2023-31484
Date: Tue, 6 Jun 2023 14:12:02 -0400 [thread overview]
Message-ID: <7daf0202-d27a-32be-8b46-3f4763720ce4@windriver.com> (raw)
In-Reply-To: <BYAPR11MB339703E6629D812AD19D49C28152A@BYAPR11MB3397.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 2309 bytes --]
On 2023-06-06 07:38, Soumya via lists.openembedded.org wrote:
> This is for kirkstone branch. Attached is the updated patch.
>
Soumya,
We don't usually take patches as attachments since we
like to see the changes in email easily for review so
unless Steve makes an exception this time, please
resend following the workflow documented here:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
See and read the section mentioning:
git send-email ... --subject-prefix="<BRANCH_NAME>][PATCH"
and the rest of the document and links therein.
../Randy
>
> Regards,
> Soumya
>
> ------------------------------------------------------------------------
> *From:* Richard Purdie <richard.purdie@linuxfoundation.org>
> *Sent:* Tuesday, June 6, 2023 4:35 PM
> *To:* Sambu, Soumya <Soumya.Sambu@windriver.com>;
> openembedded-core@lists.openembedded.org
> <openembedded-core@lists.openembedded.org>
> *Subject:* Re: [OE-core] [PATCH] perl: fix CVE-2023-31484
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender
> and know the content is safe.
>
> On Mon, 2023-06-05 at 17:46 +0000, Soumya via lists.openembedded.org
> wrote:
> > CPAN.pm before 2.35 does not verify TLS certificates when downloading
> > distributions over HTTPS.
> >
> > Signed-off-by: Soumya <soumya.sambu@windriver.com>
> > ---
> > .../perl/files/CVE-2023-31484.patch | 29 +++++++++++++++++++
> > meta/recipes-devtools/perl/perl_5.34.1.bb | 1 +
> > 2 files changed, 30 insertions(+)
> > create mode 100644
> meta/recipes-devtools/perl/files/CVE-2023-31484.patch
>
> Which release is this patch against?
>
> Cheers,
>
> Richard
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#182426):https://lists.openembedded.org/g/openembedded-core/message/182426
> Mute This Topic:https://lists.openembedded.org/mt/99345985/3616765
> Group Owner:openembedded-core+owner@lists.openembedded.org
> Unsubscribe:https://lists.openembedded.org/g/openembedded-core/unsub [randy.macleod@windriver.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
--
# Randy MacLeod
# Wind River Linux
[-- Attachment #2: Type: text/html, Size: 5666 bytes --]
next prev parent reply other threads:[~2023-06-06 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 17:46 [PATCH] perl: fix CVE-2023-31484 Soumya
2023-06-06 11:05 ` [OE-core] " Richard Purdie
2023-06-06 11:38 ` Sambu, Soumya
2023-06-06 18:12 ` Randy MacLeod [this message]
2023-06-07 5:57 ` Sambu, Soumya
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=7daf0202-d27a-32be-8b46-3f4763720ce4@windriver.com \
--to=randy.macleod@windriver.com \
--cc=Archana.Polampalli@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=soumya.sambu@windriver.com \
--cc=steve@sakoman.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;
as well as URLs for NNTP newsgroup(s).