From: Mimi Zohar <zohar@linux.ibm.com>
To: Coiby Xu <coxu@redhat.com>
Cc: linux-integrity@vger.kernel.org,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
Paul Moore <paul@paul-moore.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
"open list:SECURITY SUBSYSTEM"
<linux-security-module@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ima: require signed IMA policy when UEFI secure boot is enabled
Date: Thu, 20 Jul 2023 10:12:35 -0400 [thread overview]
Message-ID: <b6a0475c67e975cf564e4b78830ae0e598c584ac.camel@linux.ibm.com> (raw)
In-Reply-To: <kglacif5fwh3byrjkmlzygpnaecdb2zxh6hbglnvdbsfu7hbxm@gc3mjr37mnpb>
On Fri, 2023-07-14 at 09:29 +0800, Coiby Xu wrote:
> On Tue, Jul 04, 2023 at 08:57:10AM -0400, Mimi Zohar wrote:
> >On Mon, 2023-07-03 at 19:54 +0800, Coiby Xu wrote:
> >> With the introduction of the .machine keyring for UEFI-based systems,
> >> users are able to add custom CAs keys via MOK. This allow users to sign
> >> their own IMA polices. For the sake of security, mandate signed IMA
> >> policy when UEFI secure boot is enabled.
> >>
> >> Suggested-by: Mimi Zohar <zohar@linux.ibm.com>
> >> Signed-off-by: Coiby Xu <coxu@redhat.com>
With commit 099f26f22f58 ("integrity: machine keyring CA
configuration") it is now possible to require signed IMA policies
without having to recompile the kernel. Please note this change might
affect existing users/tests.
> >> ---
> >> security/integrity/ima/ima_efi.c | 3 +++
> >> 1 file changed, 3 insertions(+)
> >>
> >> diff --git a/security/integrity/ima/ima_efi.c b/security/integrity/ima/ima_efi.c
> >> index 9db66fe310d4..bb2881759505 100644
> >> --- a/security/integrity/ima/ima_efi.c
> >> +++ b/security/integrity/ima/ima_efi.c
> >> @@ -58,6 +58,9 @@ static const char * const sb_arch_rules[] = {
> >> #if !IS_ENABLED(CONFIG_MODULE_SIG)
> >> "appraise func=MODULE_CHECK appraise_type=imasig",
> >> #endif
> >> +#if IS_ENABLED(CONFIG_INTEGRITY_MACHINE_KEYRING) && IS_ENABLED(CONFIG_IMA_KEYRINGS_PERMIT_SIGNED_BY_BUILTIN_OR_SECONDARY)
> >> + "appraise func=POLICY_CHECK appraise_type=imasig",
> >> +#endif /* CONFIG_INTEGRITY_MACHINE_KEYRING && IMA_KEYRINGS_PERMIT_SIGNED_BY_BUILTIN_OR_SECONDARY */
> >> "measure func=MODULE_CHECK",
> >> NULL
> >> };
> >
> >Thanks, Coiby.
>
> You are welcome!
>
> >
> >Using IS_ENABLED() is not wrong, but unnecessary. IS_BUILTIN()
> >suffices.
>
> Thanks for the reminding! When I was going to apply this suggestion, I
> noticed ima_efi.c uses IS_ENABLED for all configuration items i.e.
> CONFIG_MODULE_SIG and CONFIG_KEXEC_SIG which are all of bool type. Would
> you like me to switch all IS_ENABLEs to IS_BUILTIN or still use
> IS_ENABLED? While IS_BUILTIN is exclusively for bool type, it's not as
> intuitive as IS_ENABLED. So it's not easy for me to make a choice.
Sure, for consistency with the other rules IS_ENABLED is fine.
thanks,
Mimi
next prev parent reply other threads:[~2023-07-20 14:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 11:54 Coiby Xu
2023-07-04 12:57 ` Mimi Zohar
2023-07-14 1:29 ` Coiby Xu
2023-07-20 14:12 ` Mimi Zohar [this message]
2023-07-26 2:08 ` [PATCH v2] " Coiby Xu
2023-07-27 17:38 ` Mimi Zohar
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=b6a0475c67e975cf564e4b78830ae0e598c584ac.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=coxu@redhat.com \
--cc=dmitry.kasatkin@gmail.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=paul@paul-moore.com \
--cc=serge@hallyn.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
all inboxes | Powered by JetHome®