Skip to contentSkip to conversation

Security Working Group meeting - Wednesday January 19

DISCUSSION Joseph Reynolds 2 participants 3 messages Jan 19, 2022

lore
Share & tools
lore
#0 lore raw

This is a reminder of the OpenBMC Security Working Group meeting scheduled for this Wednesday January 19 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.

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

#1 lore raw
Quoted 3 lines · Joseph Reynolds

We'll discuss the following items on the agenda
<https://docs.google.com/document/d/1b7x9BaxsfcukQDqbvZsU2ehMq4xoJRQvLxxsDUWmAOI>,
and anything else that comes up:

I went through the effort to become a CNA for tcpdump.org. Lots of stupid marketing overhead as mitre thinks they need to tell your marketing people what it's about :-(

It took me many tries to generate a valid JSON file for my CVE reports, but I did finally get it. Unicast me when you get there if you need help.

--

]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     [email protected]  http://www.sandelman.ca/        |   ruby on rails    [
#2 lore raw

Re: Security Working Group meeting - Wednesday January 19 - results

In reply to Joseph Reynolds
Quoted 5 lines · Joseph Reynolds

This is a reminder of the OpenBMC Security Working Group meeting scheduled for this Wednesday January 19 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:

Attended: Joseph, Dhananjay, James Mihm, Aviram from Kameleon, Dick Wilkins, Daniil, Jiang Zhang.

1 James mentioned two topics from last time: (a) integrate OpenBMC Security Response Team (SRT) docs into github, and (2) enhance the SRT process (as the OpenBMC CNA) to follow the correct process to write CVEs.

James renewed the call to push to writeup security issues in (private repo) https://github.com/openbmc/security-response/issues <https://github.com/openbmc/security-response/issues>

We are still working on this, with the limited amount of time we have.

2 Aviram from Kameleon briefly outlined interest in an OpenBMC Root of Trust (RoT).

The RoT controls access to the flash for both the BMC and host, following WIP standards from OCP: https://www.opencompute.org/blog/ocp-security-announces-version-10-specs-for-root-of-trust <https://www.opencompute.org/blog/ocp-security-announces-version-10-specs-for-root-of-trust>

-Joseph

Quoted 6 lines

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