From: Joseph Reynolds <jrey@linux.ibm.com>
To: openbmc <openbmc@lists.ozlabs.org>
Subject: Security Working Group meeting - Wednesday September 18
Date: Tue, 17 Sep 2019 18:32:40 -0500 [thread overview]
Message-ID: <bed91be2-18f2-8572-89df-d60b4d2d8365@linux.ibm.com> (raw)
This is a reminder of the OpenBMC Security Working Group meeting
scheduled for this Wednesday September 18 at 10:00am PDT.
Current topics:
- Development work:
1. IPMI authority question -
https://lists.ozlabs.org/pipermail/openbmc/2019-August/017905.html
2. Multiple admin security question -
https://lists.ozlabs.org/pipermail/openbmc/2019-August/017910.html
- OCP Secure Firmware Development Best Practices (goo.gl/uEoAh4)
- Expired password design
Access, agenda, and notes are in the wiki:
https://github.com/openbmc/openbmc/wiki/Security-working-group
- Joseph
next reply other threads:[~2019-09-17 23:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 23:32 Joseph Reynolds [this message]
2019-09-18 20:51 ` Security Working Group meeting - Wednesday September 18 Joseph Reynolds
2021-08-18 13:54 Joseph Reynolds
2021-08-18 17:33 ` Patrick Williams
2021-08-18 19:12 ` 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=bed91be2-18f2-8572-89df-d60b4d2d8365@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).