openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Joseph Reynolds <jrey@linux.ibm.com>
To: openbmc <openbmc@lists.ozlabs.org>
Subject: Security Working Group meeting - Wednesday July 21
Date: Tue, 20 Jul 2021 17:45:53 -0500	[thread overview]
Message-ID: <cd15ec44-5c29-096b-187d-f3c05680f8a2@linux.ibm.com> (raw)

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

    See Google’s “unified vulnerability schema for open source”
    https://security.googleblog.com/2021/06/announcing-unified-vulnerability-schema.html?m=1
    <https://security.googleblog.com/2021/06/announcing-unified-vulnerability-schema.html?m=1>

 2.

    Email: Update phosphor-defaults with stronger root password hash
    algorithm -
    https://lore.kernel.org/openbmc/34f5b89a-3919-e214-a744-4277fba0bbbb@linux.ibm.com/T/#u
    <https://lore.kernel.org/openbmc/34f5b89a-3919-e214-a744-4277fba0bbbb@linux.ibm.com/T/#u>






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

             reply	other threads:[~2021-07-20 22:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-20 22:45 Joseph Reynolds [this message]
2021-07-21 19:49 ` Security Working Group meeting - Wednesday July 21 - results Joseph Reynolds
2021-07-21 21:00   ` Patrick Williams

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=cd15ec44-5c29-096b-187d-f3c05680f8a2@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).