From: "Doug Flick via groups.io" <dougflick=microsoft.com@groups.io>
To: Gerd Hoffmann <kraxel@redhat.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: Jon Maloy <jmaloy@redhat.com>
Subject: Re: [edk2-devel] pixiefail
Date: Tue, 23 Jan 2024 18:49:11 +0000 [thread overview]
Message-ID: <MN2PR21MB12478AE9F865925F46CBCE1EB3742@MN2PR21MB1247.namprd21.prod.outlook.com> (raw)
In-Reply-To: <yr34vh25hxjj2dhwlbixaa2vd3lrlmy2wtjko5zhfisjriw65w@z76kqrxwroid>
Gerd,
As a new EDK2 developer, I'm working through getting the patches up to EDK2 but I have to follow the EDK2 patch process which is not the fastest thing to follow and also not my day job. If you want to see where I am you can look at the CI Pipeline. The patches were reviewed during the GHSA process by the Infosec group and have been shipping in devices already. I'm hoping to have the patches on the mailing list by EOD. This is a great topic for ways we can speed up the review process and contribution process - particularly for security patches and it would be great to get more people actively involved in reviews and testing during creation and delivery of patches.
- Doug
-----Original Message-----
From: Gerd Hoffmann <kraxel@redhat.com>
Sent: Tuesday, January 23, 2024 8:36 AM
To: devel@edk2.groups.io; Doug Flick <dougflick@microsoft.com>
Cc: Jon Maloy <jmaloy@redhat.com>
Subject: [EXTERNAL] pixiefail
[You don't often get email from kraxel@redhat.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
Hi,
What is the state of affairs wrt. the pixiefail vulnerabilities?
The advisory is published
(https://github.com/tianocore/edk2/security/advisories/GHSA-hc6x-cw6p-gj7h),
it says the plan is to have the fixes included in the next (Feb 2024) stable tag. I see bugzilla has patches attached, most of them written by Doug Flick. There is not that much time left until code freeze starts. Shouldn't we get the ball rolling to get the patches reviewed and merged? Given that the pixiefail details where published last week it should be ok to simply send the patches to the devel list for review.
thanks & take care,
Gerd
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#114228): https://edk2.groups.io/g/devel/message/114228
Mute This Topic: https://groups.io/mt/103913088/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-01-23 18:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 16:35 [edk2-devel] pixiefail Gerd Hoffmann
2024-01-23 18:49 ` Doug Flick via groups.io [this message]
2024-01-24 14:35 ` Laszlo Ersek
2024-01-24 14:57 ` Laszlo Ersek
2024-01-24 15:20 ` vincent zimmer
2024-01-24 15:26 ` Laszlo Ersek
2024-01-24 17:05 ` Gerd Hoffmann
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-list 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=MN2PR21MB12478AE9F865925F46CBCE1EB3742@MN2PR21MB1247.namprd21.prod.outlook.com \
--to=devel@edk2.groups.io \
/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