All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Mitchell <bruce.mitchell@linux.vnet.ibm.com>
To: Andrew Jeffery <andrew@aj.id.au>,
	Joseph Reynolds <jrey@linux.ibm.com>,
	openbmc <openbmc@lists.ozlabs.org>,
	"Mihm, James" <james.mihm@intel.com>
Subject: Re: Security Working Group - Wednesday April 28 - results
Date: Wed, 28 Apr 2021 15:34:07 -0700	[thread overview]
Message-ID: <314a9521-c6f1-0951-15ea-2556ebcd5cbb@linux.vnet.ibm.com> (raw)
In-Reply-To: <63563e1e-446f-4ad6-a104-728bdaa20577@beta.fastmail.com>

On 4/28/2021 15:28, Andrew Jeffery wrote:
> 
> 
> On Thu, 29 Apr 2021, at 07:55, Bruce Mitchell wrote:
>> On 4/28/2021 15:20, Andrew Jeffery wrote:
>>>
>>>
>>> On Thu, 29 Apr 2021, at 07:01, Joseph Reynolds wrote:
>>>> On 4/27/21 4:48 PM, Joseph Reynolds wrote:
>>>>> This is a reminder of the OpenBMC Security Working Group meeting
>>>>> scheduled for this Wednesday April 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. passwordless sudo access to members of the wheel group
>>>> This customization does not match the common OpenBMC use cases.
>>>> Abandoning this commit.
>>>>
>>>> Bonus topics:
>>>>
>>>> 2. Intel Hack-a-Thon 2021 results are coming soon.
>>>
>>> What does this mean?
>>>
>>
>> I believe Intel is trying publishing the results of
>> their "Intel (security) Hack-a-Thon 2021" by the end
>> of next week.
>>
> 
> Okay, but what does that mean? Are they pushing patches? Announcing CVEs? Opening bugs?
> 
> What can we expect?
> 

OpenBMC Security Working Group Meeting Notes and Agenda are here:
https://docs.google.com/document/d/1b7x9BaxsfcukQDqbvZsU2ehMq4xoJRQvLxxsDUWmAOI/edit#heading=h.8bihrhc0925u

Anything beyond that Intel would have to state what they are doing;
James?



  reply	other threads:[~2021-04-28 22:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-27 21:48 Security Working Group - Wednesday April 28 Joseph Reynolds
2021-04-28 21:31 ` Security Working Group - Wednesday April 28 - results Joseph Reynolds
2021-04-28 22:20   ` Andrew Jeffery
2021-04-28 22:25     ` Bruce Mitchell
2021-04-28 22:28       ` Andrew Jeffery
2021-04-28 22:34         ` Bruce Mitchell [this message]
2021-04-28 22:43           ` Andrew Jeffery
2021-04-29  3:54             ` 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=314a9521-c6f1-0951-15ea-2556ebcd5cbb@linux.vnet.ibm.com \
    --to=bruce.mitchell@linux.vnet.ibm.com \
    --cc=andrew@aj.id.au \
    --cc=james.mihm@intel.com \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.