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: Re: Security Working Group meeting - Wednesday September 18 - results
Date: Wed, 18 Aug 2021 14:32:29 -0500	[thread overview]
Message-ID: <911133cc-791b-5cec-4de9-c2d9f85f7e82@linux.ibm.com> (raw)
In-Reply-To: <5dfb0b20-2c1b-8d6e-343d-2df228b3fdb3@linux.ibm.com>



On 8/18/21 8:54 AM, Joseph Reynolds wrote:
> This is a reminder of the OpenBMC Security Working Group meeting 
> scheduled for this Wednesday September 18 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:
>
Attended: Joseph Reynolds, Bruce Mitchell, James Mihm, Jiang Zhang, 
Richard Wilkins, Surya Intel, Daniil Egranov Arm

> 1. Wholesale changes to bitbake recipes were made.  See 
> https://lore.kernel.org/openbmc/YQ1FD5q8KbhbXVBK@heinlein/T/#u 
> <https://lore.kernel.org/openbmc/YQ1FD5q8KbhbXVBK@heinlein/T/#u> My 
> non-specific security concern (Joseph) is accidentally mis-configuring 
> something with these changes.

DISCUSSION: None


> 2. Gerrit review - The BMCWeb session idle timeout changed to 30 
> minutes (was 60): 
> https://gerrit.openbmc-project.xyz/c/openbmc/bmcweb/+/45658 
> <https://gerrit.openbmc-project.xyz/c/openbmc/bmcweb/+/45658>
DISCUSSION: None
> 3. Yocto is planning a security configuration guide.  See 
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=14509 
> <https://bugzilla.yoctoproject.org/show_bug.cgi?id=14509>

DISCUSSION: None

Bonus items:

4. What database?  Bugzilla?  github.com issues?

DISCUSSION:

James and Surya looked at github issues.  Will test drive github.  Need 
dashboard/query function.  Worries about accidental disclosure.

Tianocore uses bugzilla per Richard.  UEFI has a separate database (not 
bugzilla).

Use github private branches?

What development process for security code reviews (Github reviews vs 
gerrit)?

Next steps: James and Surya will come up with critical objections to 
using github issues.


5 How to add session timeouts to host console?

DISCUSSION:

See the diagram in the README under 
https://github.com/openbmc/obmc-console 
<https://github.com/openbmc/obmc-console>.

We thought obmc-console-client was the right place to implement the 
timeout mechanism.

I created https://github.com/openbmc/obmc-console/issues/18 
<https://github.com/openbmc/obmc-console/issues/18>.




>
> 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


  parent reply	other threads:[~2021-08-18 19:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-18 13:54 Security Working Group meeting - Wednesday September 18 Joseph Reynolds
2021-08-18 17:33 ` Patrick Williams
2021-08-18 19:12   ` Joseph Reynolds
2021-08-18 19:32 ` Joseph Reynolds [this message]
2021-08-19  0:49   ` Security Working Group meeting - Wednesday September 18 - results Jeremy Kerr
2021-08-20 16:19     ` Security Working Group meeting - Wednesday September 18 - results - add idle timeout 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=911133cc-791b-5cec-4de9-c2d9f85f7e82@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).