Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp190604imu; Tue, 8 Jan 2019 17:35:32 -0800 (PST) X-Google-Smtp-Source: ALg8bN6h7eGHbqnczbOFV1eGch4/MkXUsCFwvbP34iwibHncICtnywJTqx+jdNGGppCyvDIvxKYK X-Received: by 2002:a63:85c6:: with SMTP id u189mr1376808pgd.156.1546997732653; Tue, 08 Jan 2019 17:35:32 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1546997732; cv=none; d=google.com; s=arc-20160816; b=x3RjW3OCVvdUMH7lxXQbsoerRDH3mQTeHQKppCccG0Zq1xHST+IfeSVeuCjGQidF/9 3yfvMMAJf7Oqi+mqK49stRhnISInxecwNv/77LlNTvILmGZNr3AawowQuBUEzKIBk2xo rH12+u1uHCZEm8dTE+pDHTFIbDKErLxot21e7paiS+HDHEnSj+X4QkhkMZlWRO2sNzL8 NDE89bbhI53wMjKbJBMYQbgWlHmpKcFz/XZSu70SE7ootPleKiftnafm4t45nFxT1aKn HhBpIWhqg5jcSYD6ASiQBOFjasJwMy4D6Bqh31jvIB6onvFeMjkgeIED3CdRLKXtZt/+ HNgw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=VzE+V5+vyhYRD4iW9YCsV9m+w+oyNvdbsZ5WQJqFSCI=; b=if5HqvBdWxPoHwUcLU21eUc8wOkf2jlzT1tLKcrvK/99tRhHexZ7ckeuxcAXJsPykJ XF0iH0QLFfcqFUhtwxLsWXu3pHSPiSglcBVWaQJ6eq4L5CuCS7BSSzV2IzkCZgVySRzc is4iAbFoNq/kgNj0mr5owTd4XDlqvX0Xdb6jRDrGR67N6EcgCkwBCNDhWcn8xGfZR9LX akP0g9lzQ19C2nI/0kq0yOni7rd8oeZAIWovN02R4KPwThBeGip1cQwwNsdvj/3reQZW TaVB4oSSrUWvjstvBJzQV4zedVVD2B1ZZ2Qqb+TlmyiysRaCx8iMO7IUV1CleNIvEZqc GxLA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i16si64622314pgk.445.2019.01.08.17.35.16; Tue, 08 Jan 2019 17:35:32 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729248AbfAIBeI (ORCPT + 99 others); Tue, 8 Jan 2019 20:34:08 -0500 Received: from mx1.redhat.com ([209.132.183.28]:55736 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728253AbfAIBeI (ORCPT ); Tue, 8 Jan 2019 20:34:08 -0500 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 1F93937E85; Wed, 9 Jan 2019 01:34:07 +0000 (UTC) Received: from dhcp-128-65.nay.redhat.com (ovpn-12-68.pek2.redhat.com [10.72.12.68]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 66A6960E3F; Wed, 9 Jan 2019 01:33:59 +0000 (UTC) Date: Wed, 9 Jan 2019 09:33:56 +0800 From: Dave Young To: Mimi Zohar Cc: Kairui Song , linux-kernel@vger.kernel.org, dhowells@redhat.com, dwmw2@infradead.org, jwboyer@fedoraproject.org, keyrings@vger.kernel.org, jmorris@namei.org, serge@hallyn.com, bauerman@linux.ibm.com, ebiggers@google.com, nayna@linux.ibm.com, linux-security-module , linux-integrity , kexec@lists.infradead.org Subject: Re: [RFC PATCH 1/1] KEYS, integrity: Link .platform keyring to .secondary_trusted_keys Message-ID: <20190109013356.GA2610@dhcp-128-65.nay.redhat.com> References: <20190108081247.2266-1-kasong@redhat.com> <20190108081247.2266-2-kasong@redhat.com> <1546960680.19931.114.camel@linux.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1546960680.19931.114.camel@linux.ibm.com> User-Agent: Mutt/1.9.5 (2018-04-13) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.29]); Wed, 09 Jan 2019 01:34:07 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org CC kexec list On 01/08/19 at 10:18am, Mimi Zohar wrote: > [Cc'ing the LSM and integrity mailing lists] > > Repeating my comment on PATCH 0/1 here with the expanded set of > mailing lists. > > The builtin and secondary keyrings have a signature change of trust > rooted in the signed kernel image.??Adding the pre-boot keys to the > secondary keyring breaks that signature chain of trust. > > Please do NOT add the pre-boot "platform" keys to the secondary > keyring. If we regard kexec as a bootloader, it sounds natural to use the platform key to verify the signature with kexec_file_load syscall. It will be hard for user to manually sign a kernel and import the key then to reuse kexec_file_load. I think we do not care if platform key can be added to secondary or not, any suggestions how can kexec_file to use the platform key? > > Mimi > > > On Tue, 2019-01-08 at 16:12 +0800, Kairui Song wrote: > > Currently kexec may need to verify the kerne image, and the kernel image > > could be signed with third part keys which are provided by paltform or > > firmware (eg. stored in MokListRT EFI variable). And the same time, > > kexec_file_load will only verify the image agains .builtin_trusted_keys > > or .secondary_trusted_keys according to configuration, but there is no > > way for kexec_file_load to verify the image against any third part keys > > mentioned above. > > > > In ea93102f3224 ('integrity: Define a trusted platform keyring') a > > .platform keyring is introduced to store the keys provided by platform > > or firmware. And with a few following commits including 15ea0e1e3e185 > > ('efi: Import certificates from UEFI Secure Boot'), now keys required to > > verify the image is being imported to .paltform keyring, and later > > IMA-appraisal could access the keyring and verify the image. > > > > This patch links the .platform keyring to .secondary_trusted_keys so > > kexec_file_load could also leverage the .platform keyring to verify the > > kernel image. > > > > Signed-off-by: Kairui Song > > --- > > certs/system_keyring.c | 30 ++++++++++++++++++++++++++++++ > > include/keys/platform_keyring.h | 12 ++++++++++++ > > security/integrity/digsig.c | 7 +++++++ > > 3 files changed, 49 insertions(+) > > create mode 100644 include/keys/platform_keyring.h > > > > diff --git a/certs/system_keyring.c b/certs/system_keyring.c > > index 81728717523d..dcef0259e149 100644 > > --- a/certs/system_keyring.c > > +++ b/certs/system_keyring.c > > @@ -18,12 +18,14 @@ > > #include > > #include > > #include > > +#include > > #include > > > > static struct key *builtin_trusted_keys; > > #ifdef CONFIG_SECONDARY_TRUSTED_KEYRING > > static struct key *secondary_trusted_keys; > > #endif > > +static struct key *platform_keys = NULL; > > > > extern __initconst const u8 system_certificate_list[]; > > extern __initconst const unsigned long system_certificate_list_size; > > @@ -67,6 +69,12 @@ int restrict_link_by_builtin_and_secondary_trusted( > > /* Allow the builtin keyring to be added to the secondary */ > > return 0; > > > > + if (type == &key_type_keyring && > > + dest_keyring == secondary_trusted_keys && > > + payload == &platform_keys->payload) > > + /* Allow the platform keyring to be added to the secondary */ > > + return 0; > > + > > return restrict_link_by_signature(dest_keyring, type, payload, > > secondary_trusted_keys); > > } > > @@ -188,6 +196,28 @@ static __init int load_system_certificate_list(void) > > } > > late_initcall(load_system_certificate_list); > > > > +#if defined(CONFIG_INTEGRITY_PLATFORM_KEYRING) && defined(CONFIG_SECONDARY_TRUSTED_KEYRING) > > + > > +/* > > + * Link .platform keyring to .secondary_trusted_key keyring > > + */ > > +static __init int load_platform_certificate_list(void) > > +{ > > + int ret = 0; > > + platform_keys = integrity_get_platform_keyring(); > > + if (!platform_keys) { > > + return 0; > > + } > > + ret = key_link(secondary_trusted_keys, platform_keys); > > + if (ret < 0) { > > + pr_err("Failed to link platform keyring: %d", ret); > > + } > > + return 0; > > +} > > +late_initcall(load_platform_certificate_list); > > + > > +#endif > > + > > #ifdef CONFIG_SYSTEM_DATA_VERIFICATION > > > > /** > > diff --git a/include/keys/platform_keyring.h b/include/keys/platform_keyring.h > > new file mode 100644 > > index 000000000000..4f92ed6c0b42 > > --- /dev/null > > +++ b/include/keys/platform_keyring.h > > @@ -0,0 +1,12 @@ > > +#ifndef _KEYS_PLATFORM_KEYRING_H > > +#define _KEYS_PLATFORM_KEYRING_H > > + > > +#include > > + > > +#ifdef CONFIG_INTEGRITY_PLATFORM_KEYRING > > + > > +extern const struct key* __init integrity_get_platform_keyring(void); > > + > > +#endif /* CONFIG_INTEGRITY_PLATFORM_KEYRING */ > > + > > +#endif /* _KEYS_SYSTEM_KEYRING_H */ > > diff --git a/security/integrity/digsig.c b/security/integrity/digsig.c > > index f45d6edecf99..397758d4f12d 100644 > > --- a/security/integrity/digsig.c > > +++ b/security/integrity/digsig.c > > @@ -176,3 +176,10 @@ int __init integrity_load_cert(const unsigned int id, const char *source, > > pr_info("Loading X.509 certificate: %s\n", source); > > return integrity_add_key(id, data, len, perm); > > } > > + > > +#ifdef CONFIG_INTEGRITY_PLATFORM_KEYRING > > +struct key* __init integrity_get_platform_keyring(void) > > +{ > > + return keyring[INTEGRITY_KEYRING_PLATFORM]; > > +} > > +#endif > Thanks Dave