openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Parth Shukla <timevortex@google.com>
To: openbmc@lists.ozlabs.org
Subject: Security Working Group Meeting - Wed 28 October
Date: Tue, 27 Oct 2020 19:20:10 +0100	[thread overview]
Message-ID: <CAC1Cx+uC+0wX-xp=FB2D80A4HujZ=ZKKHQhGcSePbyofeo6T2A@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]

This is a reminder of the OpenBMC Security Working Group meeting scheduled
for this Wednesday October 28 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. Gerrit review BMCWeb - DoS - maximum number of  persistent sessions
   https://gerrit.openbmc-project.xyz/c/openbmc/bmcweb/+/37501
   2. (Joseph) OpenBMC list of security topics - email
   https://lists.ozlabs.org/pipermail/openbmc/2020-October/023606.html .
   The main idea is to reorganize the security wiki around this list.
   3. (Joseph) BMC Configuration wiki -
   https://github.com/openbmc/openbmc/wiki/Configuration-guide (Guide for
   BMC system integrators and BMC admins).  What is the best way to proceed?
   Get this into docs repo?
   4. Security implementation of Linux kernel livepatching.
   https://lists.ozlabs.org/pipermail/openbmc/2020-October/023723.html

Access, agenda and notes are in the wiki:
https://github.com/openbmc/openbmc/wiki/Security-working-group

Regards,
Parth

[-- Attachment #2: Type: text/html, Size: 2062 bytes --]

                 reply	other threads:[~2020-10-27 18:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAC1Cx+uC+0wX-xp=FB2D80A4HujZ=ZKKHQhGcSePbyofeo6T2A@mail.gmail.com' \
    --to=timevortex@google.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).