openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Williams <patrick@stwcx.xyz>
To: Joseph Reynolds <jrey@linux.ibm.com>
Cc: openbmc <openbmc@lists.ozlabs.org>
Subject: Re: Security Working Group meeting - Wednesday September 18
Date: Wed, 18 Aug 2021 12:33:17 -0500	[thread overview]
Message-ID: <YR1EXQVdfz3RwIso@heinlein> (raw)
In-Reply-To: <5dfb0b20-2c1b-8d6e-343d-2df228b3fdb3@linux.ibm.com>

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

On Wed, Aug 18, 2021 at 08:54:52AM -0500, Joseph Reynolds wrote:
 
> 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.

How do we ensure that any configuration you want to ensure is done,
security-wise, is covered by tests going forward?

-- 
Patrick Williams

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-08-18 17:34 UTC|newest]

Thread overview: 8+ 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 [this message]
2021-08-18 19:12   ` Joseph Reynolds
2021-08-18 19:32 ` Security Working Group meeting - Wednesday September 18 - results Joseph Reynolds
2021-08-19  0:49   ` Jeremy Kerr
2021-08-20 16:19     ` Security Working Group meeting - Wednesday September 18 - results - add idle timeout Joseph Reynolds
  -- strict thread matches above, loose matches on Subject: below --
2019-09-17 23:32 Security Working Group meeting - Wednesday September 18 Joseph Reynolds
2019-09-18 20:51 ` 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=YR1EXQVdfz3RwIso@heinlein \
    --to=patrick@stwcx.xyz \
    --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 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).