From: Joseph Reynolds <jrey@linux.ibm.com>
To: openbmc <openbmc@lists.ozlabs.org>
Subject: Security Working Group meeting - Wednesday March 16
Date: Tue, 15 Mar 2022 21:45:56 -0500 [thread overview]
Message-ID: <bcdc1bcd-857c-9110-2ecc-aa3719ce1d10@linux.ibm.com> (raw)
This is a reminder of the OpenBMC Security Working Group meeting
scheduled for this Wednesday March 16 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. Please review the phosphor audit design
https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/46023
<https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/46023>
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-03-16 2:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 2:45 Joseph Reynolds [this message]
2022-03-16 17:51 ` Security Working Group meeting - Wednesday March 16 - results Joseph Reynolds
2022-03-16 19:45 ` Michael Richardson
2022-03-18 22:23 ` Security Working Group meeting - Wednesday March 16 - results - audit log handling Joseph Reynolds
2022-03-16 23:21 ` Security Working Group meeting - Wednesday March 16 - results Patrick Williams
2022-03-18 22:49 ` Joseph Reynolds
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=bcdc1bcd-857c-9110-2ecc-aa3719ce1d10@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.