[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1348215653.5337.94.camel@linux-s257.site>
Date: Fri, 21 Sep 2012 16:20:53 +0800
From: joeyli <jlee@...e.com>
To: Matthew Garrett <mjg@...hat.com>
Cc: linux-kernel@...r.kernel.org,
linux-security-module@...r.kernel.org, linux-efi@...r.kernel.org,
Josh Boyer <jwboyer@...hat.com>
Subject: Re: [PATCH V2 07/10] Secure boot: Add a dummy kernel parameter
that will switch on Secure Boot mode
於 四,2012-09-20 於 10:41 -0400,Matthew Garrett 提到:
> From: Josh Boyer <jwboyer@...hat.com>
>
> This forcibly drops CAP_COMPROMISE_KERNEL from both cap_permitted and cap_bset
> in the init_cred struct, which everything else inherits from. This works on
> any machine and can be used to develop even if the box doesn't have UEFI.
>
> Signed-off-by: Josh Boyer <jwboyer@...hat.com>
Patch works to me for test lock the IO port access.
Tested-by: Lee, Chun-Yi <jlee@...e.com>
Joey Lee
> ---
> kernel/cred.c | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
>
> diff --git a/kernel/cred.c b/kernel/cred.c
> index de728ac..7e6e83f 100644
> --- a/kernel/cred.c
> +++ b/kernel/cred.c
> @@ -623,6 +623,23 @@ void __init cred_init(void)
> 0, SLAB_HWCACHE_ALIGN|SLAB_PANIC, NULL);
> }
>
> +void __init secureboot_enable()
> +{
> + pr_info("Secure boot enabled\n");
> + cap_lower((&init_cred)->cap_bset, CAP_COMPROMISE_KERNEL);
> + cap_lower((&init_cred)->cap_permitted, CAP_COMPROMISE_KERNEL);
> +}
> +
> +/* Dummy Secure Boot enable option to fake out UEFI SB=1 */
> +static int __init secureboot_enable_opt(char *str)
> +{
> + int sb_enable = !!simple_strtol(str, NULL, 0);
> + if (sb_enable)
> + secureboot_enable();
> + return 1;
> +}
> +__setup("secureboot_enable=", secureboot_enable_opt);
> +
> /**
> * prepare_kernel_cred - Prepare a set of credentials for a kernel service
> * @daemon: A userspace daemon to be used as a reference
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists