From: Patrick Williams <patrick@stwcx.xyz>
To: "Bills, Jason M" <jason.m.bills@linux.intel.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: meta-security and DISTRO_FEATURES
Date: Fri, 6 Aug 2021 10:40:49 -0500 [thread overview]
Message-ID: <YQ1YAd1SraK9el8x@heinlein> (raw)
In-Reply-To: <3403ce92-825e-cbfc-1e53-334765134df5@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]
On Fri, Aug 06, 2021 at 09:32:45AM -0600, Bills, Jason M wrote:
> Hi All,
>
> I am getting a warning about meta-security when building:
> WARNING: You have included the meta-security layer, but 'security' has
> not been enabled in your DISTRO_FEATURES. Some bbappend files and
> preferred version setting may not take effect. See the meta-security
> README for details on enabling security support.
>
> I checked in the README and it recommends adding 'DISTRO_FEATURES_append
> = " security"' to a config file to enable all the security features.
>
> I did a quick grep on our layers and don't see that added anywhere.
> Does anyone know if this is something that we need or want to enable?
> If so, should we enable it in a common layer or will each individual
> layer decide whether to enable it?
There is this pending commit to handle it at a meta-phosphor level. I think
we're just waiting on a minor spelling fix in the variable name upstream.
https://gerrit.openbmc-project.xyz/c/openbmc/openbmc/+/45322
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-08-06 15:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-06 15:32 meta-security and DISTRO_FEATURES Bills, Jason M
2021-08-06 15:40 ` Patrick Williams [this message]
2021-08-07 1:16 ` George Liu
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=YQ1YAd1SraK9el8x@heinlein \
--to=patrick@stwcx.xyz \
--cc=jason.m.bills@linux.intel.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).