From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Michal Suchanek" <msuchanek@suse.de>, <linux-integrity@vger.kernel.org>
Cc: "Mimi Zohar" <zohar@linux.ibm.com>,
"Dmitry Kasatkin" <dmitry.kasatkin@gmail.com>,
"Paul Moore" <paul@paul-moore.com>,
"James Morris" <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
<linux-security-module@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, "joeyli" <jlee@suse.com>
Subject: Re: [PATCH] integrity: powerpc: Do not select CA_MACHINE_KEYRING
Date: Tue, 12 Sep 2023 00:45:35 +0300 [thread overview]
Message-ID: <CVGF1AQT9WI4.2660NVII9NIDU@suppilovahvero> (raw)
In-Reply-To: <20230907165224.32256-1-msuchanek@suse.de>
On Thu Sep 7, 2023 at 7:52 PM EEST, Michal Suchanek wrote:
> No other platform needs CA_MACHINE_KEYRING, either.
>
> This is policy that should be decided by the administrator, not Kconfig
s/administrator/distributor/ ?
> dependencies.
>
> cc: joeyli <jlee@suse.com>
> Signed-off-by: Michal Suchanek <msuchanek@suse.de>
> ---
> security/integrity/Kconfig | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/security/integrity/Kconfig b/security/integrity/Kconfig
> index 232191ee09e3..b6e074ac0227 100644
> --- a/security/integrity/Kconfig
> +++ b/security/integrity/Kconfig
> @@ -68,8 +68,6 @@ config INTEGRITY_MACHINE_KEYRING
> depends on INTEGRITY_ASYMMETRIC_KEYS
> depends on SYSTEM_BLACKLIST_KEYRING
> depends on LOAD_UEFI_KEYS || LOAD_PPC_KEYS
> - select INTEGRITY_CA_MACHINE_KEYRING if LOAD_PPC_KEYS
> - select INTEGRITY_CA_MACHINE_KEYRING_MAX if LOAD_PPC_KEYS
> help
> If set, provide a keyring to which Machine Owner Keys (MOK) may
> be added. This keyring shall contain just MOK keys. Unlike keys
> --
> 2.41.0
I'd suggest to add even fixes tag.
BR, Jarkko
next prev parent reply other threads:[~2023-09-12 2:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 16:52 [PATCH] integrity: powerpc: Do not select CA_MACHINE_KEYRING Michal Suchanek
2023-09-07 17:32 ` Michal Suchánek
2023-09-12 3:39 ` Nayna
2023-09-12 7:41 ` Michal Suchánek
2023-09-12 9:49 ` Jarkko Sakkinen
2023-09-12 19:22 ` Mimi Zohar
2023-09-12 19:32 ` Jarkko Sakkinen
2023-09-12 19:56 ` Mimi Zohar
2023-09-12 17:03 ` Jarkko Sakkinen
2023-09-11 21:45 ` Jarkko Sakkinen [this message]
2023-09-12 7:51 ` Michal Suchánek
2023-09-12 9:46 ` Jarkko Sakkinen
2023-09-12 10:20 ` Michal Suchánek
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=CVGF1AQT9WI4.2660NVII9NIDU@suppilovahvero \
--to=jarkko@kernel.org \
--cc=dmitry.kasatkin@gmail.com \
--cc=jlee@suse.com \
--cc=jmorris@namei.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=msuchanek@suse.de \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=zohar@linux.ibm.com \
/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).