public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gerd Hoffmann" <kraxel@redhat.com>
To: Vincent Zimmer <vincent.zimmer@gmail.com>
Cc: devel@edk2.groups.io, lersek@redhat.com, dougflick@microsoft.com,
	 Jon Maloy <jmaloy@redhat.com>
Subject: Re: [edk2-devel] pixiefail
Date: Wed, 24 Jan 2024 18:05:36 +0100	[thread overview]
Message-ID: <plriyxe4srbwsojjvdlu2tsmda5oysgz4f2thlafho2p5ymv6f@dobj4m3ahvd6> (raw)
In-Reply-To: <CAKhbih69VqkQ6g0mU-Q=6Q8C3XjKRo=Y2zED+y=uBrexAf=YeQ@mail.gmail.com>

On Wed, Jan 24, 2024 at 07:20:34AM -0800, Vincent Zimmer wrote:
> I agree on your sentiment about Bugzilla (bz) not being ideal for this.
> This space has been a multi-year journey from usrt-based tickets, bespoke
> advisories, bz, etc into today's world of tianocore infosec, tianocore as
> its own CVE Naming Authority (CNA) and working to leverage the extant
> features of github. On that latter point, there is work afoot to evolve
> from the present bz-based process
> https://github.com/tianocore/tianocore.github.io/wiki/Reporting-Security-Issues
> to a github-based one
> https://github.com/tianocore/tianocore.github.io/wiki/GHSA-GitHub-Security-Advisories-Proceess-(Draft).
> Things are in transition now and I'd echo Doug's sentiment that getting
> more feedback and engagement from the community would be valuable in
> getting the various parts tested, evolved, documented, reviewed, etc.

The GHSA process certainly is an improvement over using patches attached
to bugzilla.  There still is room for improvement though.  Community
engagement is a problem indeed, and my overall impression is that it is
even worse than on the edk2 devel list.

I think part of the problem might be lack of notifications.  I can't
remember being notified in case the "tianocore infosec team" group is
added to a new GHSA, so it's hard to learn about new advisories ...

take care,
  Gerd



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#114332): https://edk2.groups.io/g/devel/message/114332
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]
-=-=-=-=-=-=-=-=-=-=-=-



      parent reply	other threads:[~2024-01-24 17:05 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
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 [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-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=plriyxe4srbwsojjvdlu2tsmda5oysgz4f2thlafho2p5ymv6f@dobj4m3ahvd6 \
    --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