public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gerd Hoffmann" <kraxel@redhat.com>
To: devel@edk2.groups.io, dougflick@microsoft.com
Cc: Jon Maloy <jmaloy@redhat.com>
Subject: [edk2-devel] pixiefail
Date: Tue, 23 Jan 2024 17:35:49 +0100	[thread overview]
Message-ID: <yr34vh25hxjj2dhwlbixaa2vd3lrlmy2wtjko5zhfisjriw65w@z76kqrxwroid> (raw)

  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 (#114216): https://edk2.groups.io/g/devel/message/114216
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]
-=-=-=-=-=-=-=-=-=-=-=-



             reply	other threads:[~2024-01-23 16:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-23 16:35 Gerd Hoffmann [this message]
2024-01-23 18:49 ` [edk2-devel] pixiefail Doug Flick via groups.io
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=yr34vh25hxjj2dhwlbixaa2vd3lrlmy2wtjko5zhfisjriw65w@z76kqrxwroid \
    --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