From: Gyorgy Sarvari <skandigraun@gmail.com>
To: "Marko, Peter" <Peter.Marko@siemens.com>,
"openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] [meta-webserver][kirkstone][PATCH v2] nginx: patch CVE-2026-1642
Date: Mon, 23 Feb 2026 20:16:32 +0100 [thread overview]
Message-ID: <aebd2667-0e65-4119-a046-e99c362f7a31@gmail.com> (raw)
In-Reply-To: <AS1PR10MB5697D606D4AE7CD3B8A158B0FD77A@AS1PR10MB5697.EURPRD10.PROD.OUTLOOK.COM>
On 2/23/26 17:50, Marko, Peter wrote:
>> -----Original Message-----
>> From: Gyorgy Sarvari <skandigraun@gmail.com>
>> Sent: Monday, February 23, 2026 9:08
>> To: Marko, Peter (FT D EU SK BFS1) <Peter.Marko@siemens.com>;
>> openembedded-devel@lists.openembedded.org
>> Subject: Re: [oe] [meta-webserver][kirkstone][PATCH v2] nginx: patch CVE-2026-
>> 1642
>>
>> I wonder, does this patch apply only to 1.24, or does it apply to the
>> other two recipes also (and it could be just shoved into the .inc file)?
> I have sent additional patch to move both CVE patches to the inc file.
> Peter
Thanks!
prev parent reply other threads:[~2026-02-23 19:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-22 22:52 [meta-webserver][kirkstone][PATCH v2] nginx: patch CVE-2026-1642 Peter Marko
2026-02-23 8:08 ` [oe] " Gyorgy Sarvari
2026-02-23 16:50 ` Marko, Peter
2026-02-23 19:16 ` Gyorgy Sarvari [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=aebd2667-0e65-4119-a046-e99c362f7a31@gmail.com \
--to=skandigraun@gmail.com \
--cc=Peter.Marko@siemens.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.