From: "Ranjitsinh Rathod" <ranjitsinhrathod1991@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [master][kirkstone] lua: fix CVE-2022-28805
Date: Sun, 24 Apr 2022 23:15:31 -0700 [thread overview]
Message-ID: <18138.1650867331399896737@lists.openembedded.org> (raw)
In-Reply-To: <9d7e2301b84cc6cd46bdd831fdac6debfb3ee512.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 150 bytes --]
Hi Steve,
Can you please cherry-pick this on the dunfell branch as well for this Lua CVE? or should I send a patch for this?
Ranjitsinh Rathod
[-- Attachment #2: Type: text/html, Size: 166 bytes --]
next prev parent reply other threads:[~2022-04-25 19:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1650303227.git.steve@sakoman.com>
2022-04-18 19:04 ` [OE-core][master][kirkstone] busybox: fix CVE-2022-28391 Steve Sakoman
2022-04-18 19:04 ` [OE-core][master][kirkstone] lua: fix CVE-2022-28805 Steve Sakoman
2022-04-19 13:17 ` Richard Purdie
2022-04-25 6:15 ` Ranjitsinh Rathod [this message]
2022-04-25 13:57 ` [OE-core] [master][kirkstone] " Steve Sakoman
[not found] ` <16E92852A324797A.4937@lists.openembedded.org>
2022-04-25 15:08 ` Steve Sakoman
2022-04-25 15:29 ` Ranjitsinh Rathod
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=18138.1650867331399896737@lists.openembedded.org \
--to=ranjitsinhrathod1991@gmail.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox