From: Joseph Reynolds <jrey@linux.ibm.com>
To: openbmc <openbmc@lists.ozlabs.org>
Subject: Security Working Group meeting - Wednesday September 29
Date: Tue, 28 Sep 2021 20:35:03 -0500 [thread overview]
Message-ID: <bb3c031e-cbe3-36c5-0db6-d1ef454300fd@linux.ibm.com> (raw)
This is a reminder of the OpenBMC Security Working Group meeting
scheduled for this Wednesday September 29 at 10:00am PDT.
We'll discuss the following items on the agenda
<https://docs.google.com/document/d/1b7x9BaxsfcukQDqbvZsU2ehMq4xoJRQvLxxsDUWmAOI/edit>,
and anything else that comes up:
1. Continue discussion: Password based auth for IPMI over DTLS
https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/31548
<https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/31548>
2. (Joseph) Who wants a function to enable/disable BMC USB ports?
https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-dbus-interfaces/+/47180
<https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-dbus-interfaces/+/47180>
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:[~2021-09-29 1:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 1:35 Joseph Reynolds [this message]
2021-10-04 15:15 ` Security Working Group meeting - Wednesday September 29 Joseph Reynolds
2021-10-04 21:47 ` SPAKE, DTLS and passwords Michael Richardson
2021-10-05 14:50 ` Joseph Reynolds
2021-10-05 15:09 ` Michael Richardson
2021-10-05 16:22 ` Joseph Reynolds
2021-10-05 15:24 ` SPAKE, DTLS and passwords + aPAKE and SCRAM Joseph Reynolds
2021-10-13 20:51 ` Vernon Mauery
2021-10-13 20:51 ` SPAKE, DTLS and passwords Vernon Mauery
2021-10-04 21:49 ` Security Working Group meeting - Wednesday September 29 Michael Richardson
2021-10-04 22:08 ` Bruce Mitchell
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=bb3c031e-cbe3-36c5-0db6-d1ef454300fd@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).