From: Joseph Reynolds <jrey@linux.ibm.com>
To: openbmc <openbmc@lists.ozlabs.org>
Subject: Security Working Group meeting - Wednesday August 17
Date: Tue, 16 Aug 2022 22:07:52 -0500 [thread overview]
Message-ID: <772c9b0d-c06e-e4bc-b114-45a413926092@linux.ibm.com> (raw)
This is a reminder of the OpenBMC Security Working Group meeting
scheduled for this Wednesday August 17 at 10:00am PDT.
We'll discuss the following items on the agenda
<https://docs.google.com/document/d/1b7x9BaxsfcukQDqbvZsU2ehMq4xoJRQvLxxsDUWmAOI>,
and anything else that comes up:
1. Continue discussing Measured Boot.
2. Continue discussing CVE response.
3. BMC FIPS compliance.
4. Add guidance to
https://github.com/openbmc/docs/blob/master/security/how-to-report-a-security-vulnerability.md
<https://github.com/openbmc/docs/blob/master/security/how-to-report-a-security-vulnerability.md>for
submitting proof-of-concept exploits.
Access, agenda and notes are in the wiki:
https://github.com/openbmc/openbmc/wiki/Security-working-group
<https://github.com/openbmc/openbmc/wiki/Security-working-group>
- Joseph
next reply other threads:[~2022-08-17 3:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 3:07 Joseph Reynolds [this message]
2022-08-17 5:11 ` Security Working Group meeting - Wednesday August 17 Andrew Jeffery
2022-08-17 16:13 ` Joseph Reynolds
2022-08-17 16:57 ` Brad Bishop
2022-08-17 20:11 ` Joseph Reynolds
2022-08-17 20:26 ` Security Working Group meeting - moved to Discord Voice channel Joseph Reynolds
2023-08-28 19:56 ` Security Working Group meeting - regular meetings discontinued Joseph Reynolds
2022-08-17 20:29 ` Security Working Group meeting - Wednesday August 17 Patrick Williams
-- strict thread matches above, loose matches on Subject: below --
2022-08-17 17:40 Nick Rivers
2022-08-17 17:47 ` Brad Bishop
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=772c9b0d-c06e-e4bc-b114-45a413926092@linux.ibm.com \
--to=jrey@linux.ibm.com \
--cc=openbmc@lists.ozlabs.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.