openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Joseph Reynolds <jrey@linux.ibm.com>
To: openbmc@lists.ozlabs.org, krtaylor <kurt.r.taylor@gmail.com>
Subject: Re: Security Working Group Meeting - Wed 14 October - request for security bug tracker
Date: Thu, 15 Oct 2020 09:22:20 -0500	[thread overview]
Message-ID: <d29bfcde-bf3f-b739-20b3-c63686f3f746@linux.ibm.com> (raw)
In-Reply-To: <0c8a7bd5-e437-6460-b309-c9146477e120@linux.ibm.com>

On 10/15/20 9:14 AM, Joseph Reynolds wrote:
> On 10/13/20 2:06 PM, Parth Shukla wrote:
>> This is a reminder of the OpenBMC Security Working Group meeting 
>> scheduled for this...
>> This Message Is From an External Sender
>> This message came from outside your organization.
>>
>> This is a reminder of the OpenBMC Security Working Group meeting 
>> scheduled for this Wednesday October 14 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:
>>
...snip...
>
> Two subtopics were discussed:
>
> 2A. We reviewed the security reporting and bug fixing process. 
> Specifically:
>
>  * The OpenBMC security response team:
> https://github.com/openbmc/docs/blob/master/security/obmc-security-response-team.md
>
>  * This is what github advocates using:
>    https://github.com/openbmc/openbmc/security/advisories
>
>  * What tools do we use to:
>
>     * Identify which open source pkgs are used in an openbmc build,
>
>     * Identify security bugs in those packages, and
>
>     * Ensure that we pull in fixes or otherwise mitigate the problem.
>
>
> 2B. Given that OpenBMC is a Linux Foundation project, what resources 
> does the Linux Foundation offer?  Specifically, we want a private 
> secure bug tracker for the OpenBMC security response team to use.

Kurt,

The OpenBMC security response team could benefit from a bug tracker to 
track security vulnerabilities that were reported to the project and not 
yet disclosed.  This is to support [1] and would have to be private and 
secure.
What is commonly used for this?  Can we do it at the project level? Can 
LF help?

- Joseph

[1]: 
https://github.com/openbmc/docs/blob/master/security/obmc-security-response-team.md


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


  reply	other threads:[~2020-10-15 14:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-13 19:06 Security Working Group Meeting - Wed 14 October Parth Shukla
2020-10-15 14:14 ` Security Working Group Meeting - Wed 14 October - results Joseph Reynolds
2020-10-15 14:22   ` Joseph Reynolds [this message]
2020-10-15 15:53     ` Security Working Group Meeting - Wed 14 October - request for security bug tracker krtaylor

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=d29bfcde-bf3f-b739-20b3-c63686f3f746@linux.ibm.com \
    --to=jrey@linux.ibm.com \
    --cc=kurt.r.taylor@gmail.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).