integrity: support including firmware ".platform" keys at build time
Subsystems (7)
PATCH v3 1/1 integrity: support including firmware ".platform" keys at build time
Some firmware support secure boot by embedding static keys to verify the Linux kernel during boot. However, these firmware do not expose an interface for the kernel to load firmware keys onto ".platform" keyring. This would prevent kernel signature verification on kexec.
For these environments, a new function load_builtin_platform_cert() is defined to load compiled in certificates onto the ".platform" keyring.
load_certificate_list() is currently used for parsing compiled in certificates to be loaded onto the .builtin or .blacklist keyrings. Export load_certificate_list() allowing it to be used for parsing compiled in ".platform" keyring certificates as well.
---
NOTE: I am wondering if we should split this patch into two:
(https://lore.kernel.org/linux-integrity/[email protected]/).
I can do so if you also prefer the same.
v3:
* Included Jarkko's feedback
** updated patch description to include approach.
** removed extern for function declaration in the .h file.
* Included load_certificate_list() within #ifdef CONFIG_KEYS condition.
v2:
* Fixed the error reported by kernel test robot
* Updated patch description based on Jarkko's feedback.
certs/Makefile | 3 ++- certs/blacklist.c | 1 - certs/common.c | 2 +- certs/common.h | 9 ------- certs/system_keyring.c | 1 - include/keys/system_keyring.h | 6 +++++ security/integrity/Kconfig | 10 +++++++ security/integrity/Makefile | 17 +++++++++++- security/integrity/digsig.c | 2 +- security/integrity/integrity.h | 6 +++++ .../integrity/platform_certs/platform_cert.S | 23 ++++++++++++++++ .../platform_certs/platform_keyring.c | 26 +++++++++++++++++++ 12 files changed, 91 insertions(+), 15 deletions(-) delete mode 100644 certs/common.h create mode 100644 security/integrity/platform_certs/platform_cert.S
certs/Makefile +2 -1
@@ -3,7 +3,8 @@ # Makefile for the linux kernel signature checking certificates. # -obj-$(CONFIG_SYSTEM_TRUSTED_KEYRING) += system_keyring.o system_certificates.o common.o +obj-$(CONFIG_KEYS) += common.o +obj-$(CONFIG_SYSTEM_TRUSTED_KEYRING) += system_keyring.o system_certificates.o obj-$(CONFIG_SYSTEM_BLACKLIST_KEYRING) += blacklist.o common.o obj-$(CONFIG_SYSTEM_REVOCATION_LIST) += revocation_certificates.o ifneq ($(CONFIG_SYSTEM_BLACKLIST_HASH_LIST),"")
certs/blacklist.c +0 -1
@@ -17,7 +17,6 @@#include <linux/uidgid.h> #include <keys/system_keyring.h> #include "blacklist.h" -#include "common.h" static struct key *blacklist_keyring;
certs/common.c +1 -1
@@ -2,7 +2,7 @@#include <linux/kernel.h> #include <linux/key.h> -#include "common.h" +#include <keys/system_keyring.h> int load_certificate_list(const u8 cert_list[], const unsigned long list_size,
certs/common.h deleted +0 -9
@@ -1,9 +0,0 @@ -/* SPDX-License-Identifier: GPL-2.0-or-later */ - -#ifndef _CERT_COMMON_H -#define _CERT_COMMON_H - -int load_certificate_list (const u8 cert_list[],const unsigned long list_size, -const struct key *keyring); - -#endif
certs/system_keyring.c +0 -1
@@ -16,7 +16,6 @@#include <keys/asymmetric-type.h> #include <keys/system_keyring.h> #include <crypto/pkcs7.h> -#include "common.h" static struct key *builtin_trusted_keys;#ifdef CONFIG_SECONDARY_TRUSTED_KEYRING
include/keys/system_keyring.h +6 -0
@@ -10,6 +10,12 @@#include <linux/key.h> +#ifdef CONFIG_KEYS +int load_certificate_list (const u8 cert_list[], +const unsigned long list_size, +const struct key *keyring); +#endif +#ifdef CONFIG_SYSTEM_TRUSTED_KEYRING extern int restrict_link_by_builtin_trusted(struct key *keyring,
security/integrity/Kconfig +10 -0
@@ -62,6 +62,16 @@ config INTEGRITY_PLATFORM_KEYRING provided by the platform for verifying the kexec'ed kerned image and, possibly, the initramfs signature. +config INTEGRITY_PLATFORM_BUILTIN_KEYS + string "Builtin X.509 keys for .platform keyring" + depends on KEYS + depends on ASYMMETRIC_KEY_TYPE + depends on INTEGRITY_PLATFORM_KEYRING + help + If set, this option should be the filename of a PEM-formatted file + containing X.509 certificates to be loaded onto the ".platform" + keyring. + config LOAD_UEFI_KEYS depends on INTEGRITY_PLATFORM_KEYRING depends on EFI
security/integrity/Makefile +16 -1
@@ -3,13 +3,18 @@ # Makefile for caching inode integrity data (iint) # +quiet_cmd_extract_certs = EXTRACT_CERTS $(patsubst "%",%,$(2)) + cmd_extract_certs = scripts/extract-cert $(2) $@ +$(eval $(call config_filename,INTEGRITY_PLATFORM_BUILTIN_KEYS)) + obj-$(CONFIG_INTEGRITY) += integrity.o integrity-y := iint.o integrity-$(CONFIG_INTEGRITY_AUDIT) += integrity_audit.o integrity-$(CONFIG_INTEGRITY_SIGNATURE) += digsig.o integrity-$(CONFIG_INTEGRITY_ASYMMETRIC_KEYS) += digsig_asymmetric.o -integrity-$(CONFIG_INTEGRITY_PLATFORM_KEYRING) += platform_certs/platform_keyring.o +integrity-$(CONFIG_INTEGRITY_PLATFORM_KEYRING) += platform_certs/platform_keyring.o \ + platform_certs/platform_cert.o integrity-$(CONFIG_LOAD_UEFI_KEYS) += platform_certs/efi_parser.o \ platform_certs/load_uefi.o \ platform_certs/keyring_handler.o
@@ -19,3 +24,13 @@ integrity-$(CONFIG_LOAD_PPC_KEYS) += platform_certs/efi_parser.o \ platform_certs/keyring_handler.o obj-$(CONFIG_IMA) += ima/ obj-$(CONFIG_EVM) += evm/ + + +$(obj)/platform_certs/platform_cert.o: $(obj)/platform_certs/platform_certificate_list + +targets += platform_certificate_list + +$(obj)/platform_certs/platform_certificate_list: scripts/extract-cert $(INTEGRITY_PLATFORM_BUILTIN_KEYS_FILENAME) FORCE + $(call if_changed,extract_certs,$(CONFIG_INTEGRITY_PLATFORM_BUILTIN_KEYS)) + +clean-files := platform_certs/platform_certificate_list
security/integrity/digsig.c +1 -1
@@ -38,7 +38,7 @@ static const char * const keyring_name[INTEGRITY_KEYRING_MAX] = {#define restrict_link_to_ima restrict_link_by_builtin_trusted#endif -static struct key *integrity_keyring_from_id (const unsigned int id) +struct key *integrity_keyring_from_id (const unsigned int id) {if (id >=INTEGRITY_KEYRING_MAX )return ERR_PTR (-EINVAL );
security/integrity/integrity.h +6 -0
@@ -167,6 +167,7 @@ int __init integrity_init_keyring(const unsigned int id);int __init integrity_load_x509 (const unsigned int id,const char *path);int __init integrity_load_cert (const unsigned int id,const char *source,const void *data,size_t len,key_perm_t perm); +struct key *integrity_keyring_from_id (const unsigned int id);#else static inline int integrity_digsig_verify(const unsigned int id,
@@ -194,6 +195,11 @@ static inline int __init integrity_load_cert(const unsigned int id, {return 0 ; } + +static inline struct key *integrity_keyring_from_id (const unsigned int id) +{ +return ERR_PTR (-EOPNOTSUPP ); +}#endif /* CONFIG_INTEGRITY_SIGNATURE */ #ifdef CONFIG_INTEGRITY_ASYMMETRIC_KEYS
security/integrity/platform_certs/platform_cert.S new file +23 -0
@@ -0,0 +1,23 @@ +/* SPDX-License-Identifier: GPL-2.0 */ +#include <linux/export.h> +#include <linux/init.h> + + __INITRODATA + + .align 8 +#ifdef CONFIG_INTEGRITY_PLATFORM_KEYRING + .globl platform_certificate_list +platform_certificate_list: +__cert_list_start: + .incbin "security/integrity/platform_certs/platform_certificate_list" +__cert_list_end: +#endif + + .align 8 + .globl platform_certificate_list_size +platform_certificate_list_size: +#ifdef CONFIG_64BIT + .quad __cert_list_end - __cert_list_start +#else + .long __cert_list_end - __cert_list_start +#endif
security/integrity/platform_certs/platform_keyring.c +26 -0
@@ -12,8 +12,12 @@#include <linux/cred.h> #include <linux/err.h> #include <linux/slab.h> +#include <keys/system_keyring.h> #include "../integrity.h" +extern __initconst const u8 platform_certificate_list[]; +extern __initconst const unsigned long platform_certificate_list_size; +/** * add_to_platform_keyring - Add to platform keyring without validation. * @source: Source of key
@@ -37,6 +41,28 @@ void __init add_to_platform_keyring(const char *source, const void *data,pr_info ("Error adding keys to platform keyring %s\n" , source); } +static __init int load_builtin_platform_cert (void ) +{ +const u8 *p; +unsigned long size; +int rc; +struct key *keyring; + + p = platform_certificate_list; + size = platform_certificate_list_size; + + keyring =integrity_keyring_from_id (INTEGRITY_KEYRING_PLATFORM ); +if (IS_ERR (keyring)) +return PTR_ERR (keyring); + + rc =load_certificate_list (p, size, keyring); +if (rc) +pr_info ("Error adding keys to platform keyring %d\n" , rc); + +return rc; +} +late_initcall (load_builtin_platform_cert); +/* * Create the trusted keyrings. */
Signature · 1 line
2.29.2
Gentle reminder for v3. Is this version good now for acceptance ?
Thanks & Regards,
- Nayna
Quoted 300 lines · Nayna Jain
Some firmware support secure boot by embedding static keys to verify the Linux kernel during boot. However, these firmware do not expose an interface for the kernel to load firmware keys onto ".platform" keyring. This would prevent kernel signature verification on kexec.
For these environments, a new function
load_builtin_platform_cert()is defined to load compiled in certificates onto the ".platform" keyring.
load_certificate_list()is currently used for parsing compiled in certificates to be loaded onto the .builtin or .blacklist keyrings. Exportload_certificate_list()allowing it to be used for parsing compiled in ".platform" keyring certificates as well.Signed-off-by Nayna Jain <[email protected]>---
NOTE: I am wondering if we should split this patch into two:
(https://lore.kernel.org/linux-integrity/[email protected]/).
I can do so if you also prefer the same.v3:
* Included Jarkko's feedback
** updated patch description to include approach.
** removed extern for function declaration in the .h file.
* Includedload_certificate_list()within #ifdefCONFIG_KEYScondition.v2:
* Fixed the error reported by kernel test robot
* Updated patch description based on Jarkko's feedback.certs/Makefile | 3 ++- certs/blacklist.c | 1 - certs/common.c | 2 +- certs/common.h | 9 ------- certs/system_keyring.c | 1 - include/keys/system_keyring.h | 6 +++++ security/integrity/Kconfig | 10 +++++++ security/integrity/Makefile | 17 +++++++++++- security/integrity/digsig.c | 2 +- security/integrity/integrity.h | 6 +++++ .../integrity/platform_certs/platform_cert.S | 23 ++++++++++++++++ .../platform_certs/platform_keyring.c | 26 +++++++++++++++++++ 12 files changed, 91 insertions(+), 15 deletions(-)delete mode 100644
certs/common.h
create mode 100644security/integrity/platform_certs/platform_cert.Scerts/Makefile +2
-1@@ -3,7 +3,8 @@ # Makefile for the linux kernel signature checking certificates. # -obj-$(CONFIG_SYSTEM_TRUSTED_KEYRING) += system_keyring.o system_certificates.o common.o +obj-$(CONFIG_KEYS) += common.o +obj-$(CONFIG_SYSTEM_TRUSTED_KEYRING) += system_keyring.o system_certificates.o obj-$(CONFIG_SYSTEM_BLACKLIST_KEYRING) += blacklist.o common.o obj-$(CONFIG_SYSTEM_REVOCATION_LIST) += revocation_certificates.o ifneq ($(CONFIG_SYSTEM_BLACKLIST_HASH_LIST),"")certs/blacklist.c +0
-1@@ -17,7 +17,6 @@#include <linux/uidgid.h> #include <keys/system_keyring.h> #include "blacklist.h" -#include "common.h" static struct key *blacklist_keyring;certs/common.c +1
-1@@ -2,7 +2,7 @@#include <linux/kernel.h> #include <linux/key.h> -#include "common.h" +#include <keys/system_keyring.h> int load_certificate_list(const u8 cert_list[], const unsigned long list_size,certs/common.h deleted +0
-9@@ -1,9 +0,0 @@ -/* SPDX-License-Identifier: GPL-2.0-or-later */ - -#ifndef _CERT_COMMON_H -#define _CERT_COMMON_H - -int load_certificate_list (const u8 cert_list[],const unsigned long list_size, -const struct key *keyring); - -#endif certs/system_keyring.c +0
-1@@ -16,7 +16,6 @@#include <keys/asymmetric-type.h> #include <keys/system_keyring.h> #include <crypto/pkcs7.h> -#include "common.h" static struct key *builtin_trusted_keys;#ifdef CONFIG_SECONDARY_TRUSTED_KEYRING include/keys/system_keyring.h +6
-0@@ -10,6 +10,12 @@#include <linux/key.h> +#ifdef CONFIG_KEYS +int load_certificate_list (const u8 cert_list[], +const unsigned long list_size, +const struct key *keyring); +#endif +#ifdef CONFIG_SYSTEM_TRUSTED_KEYRING extern int restrict_link_by_builtin_trusted(struct key *keyring,security/integrity/Kconfig +10
-0@@ -62,6 +62,16 @@ config INTEGRITY_PLATFORM_KEYRING provided by the platform for verifying the kexec'ed kerned image and, possibly, the initramfs signature. +config INTEGRITY_PLATFORM_BUILTIN_KEYS + string "Builtin X.509 keys for .platform keyring" + depends on KEYS + depends on ASYMMETRIC_KEY_TYPE + depends on INTEGRITY_PLATFORM_KEYRING + help + If set, this option should be the filename of a PEM-formatted file + containing X.509 certificates to be loaded onto the ".platform" + keyring. + config LOAD_UEFI_KEYS depends on INTEGRITY_PLATFORM_KEYRING depends on EFIsecurity/integrity/Makefile +16
-1@@ -3,13 +3,18 @@ # Makefile for caching inode integrity data (iint) # +quiet_cmd_extract_certs = EXTRACT_CERTS $(patsubst "%",%,$(2)) + cmd_extract_certs = scripts/extract-cert $(2) $@ +$(eval $(call config_filename,INTEGRITY_PLATFORM_BUILTIN_KEYS)) + obj-$(CONFIG_INTEGRITY) += integrity.o integrity-y := iint.o integrity-$(CONFIG_INTEGRITY_AUDIT) += integrity_audit.o integrity-$(CONFIG_INTEGRITY_SIGNATURE) += digsig.o integrity-$(CONFIG_INTEGRITY_ASYMMETRIC_KEYS) += digsig_asymmetric.o -integrity-$(CONFIG_INTEGRITY_PLATFORM_KEYRING) += platform_certs/platform_keyring.o +integrity-$(CONFIG_INTEGRITY_PLATFORM_KEYRING) += platform_certs/platform_keyring.o \ + platform_certs/platform_cert.o integrity-$(CONFIG_LOAD_UEFI_KEYS) += platform_certs/efi_parser.o \ platform_certs/load_uefi.o \ platform_certs/keyring_handler.o@@ -19,3 +24,13 @@ integrity-$(CONFIG_LOAD_PPC_KEYS) += platform_certs/efi_parser.o \ platform_certs/keyring_handler.o obj-$(CONFIG_IMA) += ima/ obj-$(CONFIG_EVM) += evm/ + + +$(obj)/platform_certs/platform_cert.o: $(obj)/platform_certs/platform_certificate_list + +targets += platform_certificate_list + +$(obj)/platform_certs/platform_certificate_list: scripts/extract-cert $(INTEGRITY_PLATFORM_BUILTIN_KEYS_FILENAME) FORCE + $(call if_changed,extract_certs,$(CONFIG_INTEGRITY_PLATFORM_BUILTIN_KEYS)) + +clean-files := platform_certs/platform_certificate_listsecurity/integrity/digsig.c +1
-1@@ -38,7 +38,7 @@ static const char * const keyring_name[INTEGRITY_KEYRING_MAX] = {#define restrict_link_to_ima restrict_link_by_builtin_trusted#endif -static struct key *integrity_keyring_from_id (const unsigned int id) +struct key *integrity_keyring_from_id (const unsigned int id) {if (id >=INTEGRITY_KEYRING_MAX )return ERR_PTR (-EINVAL );security/integrity/integrity.h +6
-0@@ -167,6 +167,7 @@ int __init integrity_init_keyring(const unsigned int id);int __init integrity_load_x509 (const unsigned int id,const char *path);int __init integrity_load_cert (const unsigned int id,const char *source,const void *data,size_t len,key_perm_t perm); +struct key *integrity_keyring_from_id (const unsigned int id);#else static inline int integrity_digsig_verify(const unsigned int id,@@ -194,6 +195,11 @@ static inline int __init integrity_load_cert(const unsigned int id, {return 0 ; } + +static inline struct key *integrity_keyring_from_id (const unsigned int id) +{ +return ERR_PTR (-EOPNOTSUPP ); +}#endif /* CONFIG_INTEGRITY_SIGNATURE */ #ifdef CONFIG_INTEGRITY_ASYMMETRIC_KEYS security/integrity/platform_certs/platform_cert.S new file +23
-0@@ -0,0 +1,23 @@ +/* SPDX-License-Identifier: GPL-2.0 */ +#include <linux/export.h> +#include <linux/init.h> + + __INITRODATA + + .align 8 +#ifdef CONFIG_INTEGRITY_PLATFORM_KEYRING + .globl platform_certificate_list +platform_certificate_list: +__cert_list_start: + .incbin "security/integrity/platform_certs/platform_certificate_list" +__cert_list_end: +#endif + + .align 8 + .globl platform_certificate_list_size +platform_certificate_list_size: +#ifdef CONFIG_64BIT + .quad __cert_list_end - __cert_list_start +#else + .long __cert_list_end - __cert_list_start +#endifsecurity/integrity/platform_certs/platform_keyring.c +26
-0@@ -12,8 +12,12 @@#include <linux/cred.h> #include <linux/err.h> #include <linux/slab.h> +#include <keys/system_keyring.h> #include "../integrity.h" +extern __initconst const u8 platform_certificate_list[]; +extern __initconst const unsigned long platform_certificate_list_size; +/** * add_to_platform_keyring - Add to platform keyring without validation. * @source: Source of key @@ -37,6 +41,28 @@ void __init add_to_platform_keyring(const char *source, const void *data,pr_info ("Error adding keys to platform keyring %s\n" , source); } +static __init int load_builtin_platform_cert (void ) +{ +const u8 *p; +unsigned long size; +int rc; +struct key *keyring; + + p = platform_certificate_list; + size = platform_certificate_list_size; + + keyring =integrity_keyring_from_id (INTEGRITY_KEYRING_PLATFORM ); +if (IS_ERR (keyring)) +return PTR_ERR (keyring); + + rc =load_certificate_list (p, size, keyring); +if (rc) +pr_info ("Error adding keys to platform keyring %d\n" , rc); + +return rc; +} +late_initcall (load_builtin_platform_cert); +/* * Create the trusted keyrings. */
Mimi Zohar
maintainerQuoted 26 lines · Nayna
Gentle reminder for v3. Is this version good now for acceptance ?
Thanks & Regards,
- Nayna
Quoted 19 lines · Nayna Jain
Some firmware support secure boot by embedding static keys to verify the Linux kernel during boot. However, these firmware do not expose an interface for the kernel to load firmware keys onto ".platform" keyring. This would prevent kernel signature verification on kexec.
For these environments, a new function
load_builtin_platform_cert()is defined to load compiled in certificates onto the ".platform" keyring.
load_certificate_list()is currently used for parsing compiled in certificates to be loaded onto the .builtin or .blacklist keyrings. Exportload_certificate_list()allowing it to be used for parsing compiled in ".platform" keyring certificates as well.Signed-off-by Nayna Jain <[email protected]>---
NOTE: I am wondering if we should split this patch into two:
(https://lore.kernel.org/linux-integrity/[email protected]/).
I can do so if you also prefer the same.
Yes, splitting this patch would make it easier to review and upstream.
thanks,
Mimi
(Changing Seth's email to personal domain one)
Quoted 13 lines · Nayna Jain
Some firmware support secure boot by embedding static keys to verify the Linux kernel during boot. However, these firmware do not expose an interface for the kernel to load firmware keys onto ".platform" keyring. This would prevent kernel signature verification on kexec.
For these environments, a new function
load_builtin_platform_cert()is defined to load compiled in certificates onto the ".platform" keyring.
load_certificate_list()is currently used for parsing compiled in certificates to be loaded onto the .builtin or .blacklist keyrings. Exportload_certificate_list()allowing it to be used for parsing compiled in ".platform" keyring certificates as well.
Quoted 7 lines
Signed-off-by Nayna Jain <[email protected]>---
NOTE: I am wondering if we should split this patch into two:
(https://lore.kernel.org/linux-integrity/[email protected]/).
I can do so if you also prefer the same.
Yes, i think you should split the patches into refactor & new feature. It allows one to clearly inspect/validate the no-change refactor, and separately review the newly added feature with clarity.
Or maybe avoid the refactor all together, see my optional suggestion at the end.
Quoted 211 lines
v3:
* Included Jarkko's feedback
** updated patch description to include approach.
** removed extern for function declaration in the .h file.
* Includedload_certificate_list()within #ifdefCONFIG_KEYScondition.v2:
* Fixed the error reported by kernel test robot
* Updated patch description based on Jarkko's feedback.certs/Makefile | 3 ++- certs/blacklist.c | 1 - certs/common.c | 2 +- certs/common.h | 9 ------- certs/system_keyring.c | 1 - include/keys/system_keyring.h | 6 +++++ security/integrity/Kconfig | 10 +++++++ security/integrity/Makefile | 17 +++++++++++- security/integrity/digsig.c | 2 +- security/integrity/integrity.h | 6 +++++ .../integrity/platform_certs/platform_cert.S | 23 ++++++++++++++++ .../platform_certs/platform_keyring.c | 26 +++++++++++++++++++ 12 files changed, 91 insertions(+), 15 deletions(-) delete mode 100644 certs/common.h create mode 100644 security/integrity/platform_certs/platform_cert.Scerts/Makefile +2
-1@@ -3,7 +3,8 @@ # Makefile for the linux kernel signature checking certificates. # -obj-$(CONFIG_SYSTEM_TRUSTED_KEYRING) += system_keyring.o system_certificates.o common.o +obj-$(CONFIG_KEYS) += common.o +obj-$(CONFIG_SYSTEM_TRUSTED_KEYRING) += system_keyring.o system_certificates.o obj-$(CONFIG_SYSTEM_BLACKLIST_KEYRING) += blacklist.o common.o obj-$(CONFIG_SYSTEM_REVOCATION_LIST) += revocation_certificates.o ifneq ($(CONFIG_SYSTEM_BLACKLIST_HASH_LIST),"")certs/blacklist.c +0
-1@@ -17,7 +17,6 @@#include <linux/uidgid.h> #include <keys/system_keyring.h> #include "blacklist.h" -#include "common.h" static struct key *blacklist_keyring;certs/common.c +1
-1@@ -2,7 +2,7 @@#include <linux/kernel.h> #include <linux/key.h> -#include "common.h" +#include <keys/system_keyring.h> int load_certificate_list(const u8 cert_list[], const unsigned long list_size,certs/common.h deleted +0
-9@@ -1,9 +0,0 @@ -/* SPDX-License-Identifier: GPL-2.0-or-later */ - -#ifndef _CERT_COMMON_H -#define _CERT_COMMON_H - -int load_certificate_list (const u8 cert_list[],const unsigned long list_size, -const struct key *keyring); - -#endif certs/system_keyring.c +0
-1@@ -16,7 +16,6 @@#include <keys/asymmetric-type.h> #include <keys/system_keyring.h> #include <crypto/pkcs7.h> -#include "common.h" static struct key *builtin_trusted_keys;#ifdef CONFIG_SECONDARY_TRUSTED_KEYRING include/keys/system_keyring.h +6
-0@@ -10,6 +10,12 @@#include <linux/key.h> +#ifdef CONFIG_KEYS +int load_certificate_list (const u8 cert_list[], +const unsigned long list_size, +const struct key *keyring); +#endif +#ifdef CONFIG_SYSTEM_TRUSTED_KEYRING extern int restrict_link_by_builtin_trusted(struct key *keyring,security/integrity/Kconfig +10
-0@@ -62,6 +62,16 @@ config INTEGRITY_PLATFORM_KEYRING provided by the platform for verifying the kexec'ed kerned image and, possibly, the initramfs signature. +config INTEGRITY_PLATFORM_BUILTIN_KEYS + string "Builtin X.509 keys for .platform keyring" + depends on KEYS + depends on ASYMMETRIC_KEY_TYPE + depends on INTEGRITY_PLATFORM_KEYRING + help + If set, this option should be the filename of a PEM-formatted file + containing X.509 certificates to be loaded onto the ".platform" + keyring. + config LOAD_UEFI_KEYS depends on INTEGRITY_PLATFORM_KEYRING depends on EFIsecurity/integrity/Makefile +16
-1@@ -3,13 +3,18 @@ # Makefile for caching inode integrity data (iint) # +quiet_cmd_extract_certs = EXTRACT_CERTS $(patsubst "%",%,$(2)) + cmd_extract_certs = scripts/extract-cert $(2) $@ +$(eval $(call config_filename,INTEGRITY_PLATFORM_BUILTIN_KEYS)) + obj-$(CONFIG_INTEGRITY) += integrity.o integrity-y := iint.o integrity-$(CONFIG_INTEGRITY_AUDIT) += integrity_audit.o integrity-$(CONFIG_INTEGRITY_SIGNATURE) += digsig.o integrity-$(CONFIG_INTEGRITY_ASYMMETRIC_KEYS) += digsig_asymmetric.o -integrity-$(CONFIG_INTEGRITY_PLATFORM_KEYRING) += platform_certs/platform_keyring.o +integrity-$(CONFIG_INTEGRITY_PLATFORM_KEYRING) += platform_certs/platform_keyring.o \ + platform_certs/platform_cert.o integrity-$(CONFIG_LOAD_UEFI_KEYS) += platform_certs/efi_parser.o \ platform_certs/load_uefi.o \ platform_certs/keyring_handler.o@@ -19,3 +24,13 @@ integrity-$(CONFIG_LOAD_PPC_KEYS) += platform_certs/efi_parser.o \ platform_certs/keyring_handler.o obj-$(CONFIG_IMA) += ima/ obj-$(CONFIG_EVM) += evm/ + + +$(obj)/platform_certs/platform_cert.o: $(obj)/platform_certs/platform_certificate_list + +targets += platform_certificate_list + +$(obj)/platform_certs/platform_certificate_list: scripts/extract-cert $(INTEGRITY_PLATFORM_BUILTIN_KEYS_FILENAME) FORCE + $(call if_changed,extract_certs,$(CONFIG_INTEGRITY_PLATFORM_BUILTIN_KEYS)) + +clean-files := platform_certs/platform_certificate_listsecurity/integrity/digsig.c +1
-1@@ -38,7 +38,7 @@ static const char * const keyring_name[INTEGRITY_KEYRING_MAX] = {#define restrict_link_to_ima restrict_link_by_builtin_trusted#endif -static struct key *integrity_keyring_from_id (const unsigned int id) +struct key *integrity_keyring_from_id (const unsigned int id) {if (id >=INTEGRITY_KEYRING_MAX )return ERR_PTR (-EINVAL );security/integrity/integrity.h +6
-0@@ -167,6 +167,7 @@ int __init integrity_init_keyring(const unsigned int id);int __init integrity_load_x509 (const unsigned int id,const char *path);int __init integrity_load_cert (const unsigned int id,const char *source,const void *data,size_t len,key_perm_t perm); +struct key *integrity_keyring_from_id (const unsigned int id);#else static inline int integrity_digsig_verify(const unsigned int id,@@ -194,6 +195,11 @@ static inline int __init integrity_load_cert(const unsigned int id, {return 0 ; } + +static inline struct key *integrity_keyring_from_id (const unsigned int id) +{ +return ERR_PTR (-EOPNOTSUPP ); +}#endif /* CONFIG_INTEGRITY_SIGNATURE */ #ifdef CONFIG_INTEGRITY_ASYMMETRIC_KEYS security/integrity/platform_certs/platform_cert.S new file +0
-0
security/integrity/platform_certs/platform_cert.S line 1
Quoted 1 line
security/integrity/platform_certs/platform_cert.S new file +1
-0@@ -0,0 +1,23 @@ +/* SPDX-License-Identifier: GPL-2.0 */
My personal preference would be to have platform_cert.S next to all the other "extract certs and build an object out of them", as in /certs/platform_cert.S right next to the other similar .S files, i.e system_certificates.S and revocation_certificates.S it would make it easier to inspect the build and find all the various types of built-in keys.
This is a minor comment/suggestion, that you can reject.
Quoted 40 lines
security/integrity/platform_certs/platform_cert.S new file +22
-0+#include <linux/export.h> +#include <linux/init.h> + + __INITRODATA + + .align 8 +#ifdef CONFIG_INTEGRITY_PLATFORM_KEYRING + .globl platform_certificate_list +platform_certificate_list: +__cert_list_start: + .incbin "security/integrity/platform_certs/platform_certificate_list" +__cert_list_end: +#endif + + .align 8 + .globl platform_certificate_list_size +platform_certificate_list_size: +#ifdef CONFIG_64BIT + .quad __cert_list_end - __cert_list_start +#else + .long __cert_list_end - __cert_list_start +#endifsecurity/integrity/platform_certs/platform_keyring.c +4
-0@@ -12,8 +12,12 @@#include <linux/cred.h> #include <linux/err.h> #include <linux/slab.h> +#include <keys/system_keyring.h> #include "../integrity.h" +extern __initconst const u8 platform_certificate_list[]; +extern __initconst const unsigned long platform_certificate_list_size; +/** * add_to_platform_keyring - Add to platform keyring without validation. * @source: Source of key
security/integrity/platform_certs/platform_keyring.c void __init add_to_platform_keyring(const char *source, const void *data, · line 43
Quoted 3 lines
security/integrity/platform_certs/platform_keyring.c +0
-0@@ -37,6 +41,28 @@ void __init add_to_platform_keyring(const char *source, const void *data,pr_info ("Error adding keys to platform keyring %s\n" , source); }
I think the below hunk should be guarded with #ifdef CONFIG_INTEGRITY_PLATFORM_BUILTIN_KEYS, similar to how similar call is ifdef'ed in case of revocation keys i.e. see ifdef CONFIG_SYSTEM_REVOCATION_LIST in certs/blacklist.c. Because one can configure a kernel with a platform keyring, but without platform builtin keys.
I think this must be be fixed.
Quoted 12 lines
security/integrity/platform_certs/platform_keyring.c +12
-0+static __init int load_builtin_platform_cert (void ) +{ +const u8 *p; +unsigned long size; +int rc; +struct key *keyring; + + p = platform_certificate_list; + size = platform_certificate_list_size; + + keyring =integrity_keyring_from_id (INTEGRITY_KEYRING_PLATFORM ); +if (IS_ERR (keyring))
security/integrity/platform_certs/platform_keyring.c void __init add_to_platform_keyring(const char *source, const void *data, · line 65
Quoted 10 lines
security/integrity/platform_certs/platform_keyring.c +10
-0+return PTR_ERR (keyring); + + rc =load_certificate_list (p, size, keyring); +if (rc) +pr_info ("Error adding keys to platform keyring %d\n" , rc); + +return rc; +} +late_initcall (load_builtin_platform_cert); +
Some more general comment:
I do wonder if the refactor of load_certificate_list can be somehow avoided. For example, when platform keyring is allocated it calls set_platform_trusted_keys() from certs/system-keyring.c which could add a call to load_builtin_platform_cert, and it already has a handle to the platform keyring. The set_platform_trusted_keys() could call to load_certificate_list there without late_initcall, alocating variables, and looking up the integrity_keyring_from id. It would make this feature patch very concise and straight forward then.
That way builtin platform certs will be done before platform specific load_*.c things are done. But also it will make builtin certs loading be done in a different place from the rest of the platform certs loading (e.g. the uefi one). So maybe doing builtin certs loading, next to all other platform cert loading makes sense, despite it being away from other builtin certs loading into other keyrings.
I am divided on this =)
security/integrity/platform_certs/platform_keyring.c void __init add_to_platform_keyring(const char *source, const void *data, · line 68
Quoted 4 lines
security/integrity/platform_certs/platform_keyring.c +0
-0/* * Create the trusted keyrings. */
Regards,
Dimitri.
Quoted 23 lines · Dimitri John Ledkov
(Changing Seth's email to personal domain one)
Quoted 13 lines · Nayna Jain
Some firmware support secure boot by embedding static keys to verify the Linux kernel during boot. However, these firmware do not expose an interface for the kernel to load firmware keys onto ".platform" keyring. This would prevent kernel signature verification on kexec.
For these environments, a new function
load_builtin_platform_cert()is defined to load compiled in certificates onto the ".platform" keyring.
load_certificate_list()is currently used for parsing compiled in certificates to be loaded onto the .builtin or .blacklist keyrings. Exportload_certificate_list()allowing it to be used for parsing compiled in ".platform" keyring certificates as well.Quoted 7 lines
Signed-off-by Nayna Jain <[email protected]>---
NOTE: I am wondering if we should split this patch into two:
(https://lore.kernel.org/linux-integrity/[email protected]/).
I can do so if you also prefer the same.
Quoted 6 lines
Yes, i think you should split the patches into refactor & new feature. It allows one to clearly inspect/validate the no-change refactor, and separately review the newly added feature with clarity.
Or maybe avoid the refactor all together, see my optional suggestion at the end.
Thanks Dimitri for the feedback. Sorry for the delay in the response, I was on vacation last week. Yes, I have split the patches now for next version. Answers to other comments are inline.
Quoted 218 lines
Quoted 211 lines
v3:
* Included Jarkko's feedback
** updated patch description to include approach.
** removed extern for function declaration in the .h file.
* Includedload_certificate_list()within #ifdefCONFIG_KEYScondition.v2:
* Fixed the error reported by kernel test robot
* Updated patch description based on Jarkko's feedback.certs/Makefile | 3 ++- certs/blacklist.c | 1 - certs/common.c | 2 +- certs/common.h | 9 ------- certs/system_keyring.c | 1 - include/keys/system_keyring.h | 6 +++++ security/integrity/Kconfig | 10 +++++++ security/integrity/Makefile | 17 +++++++++++- security/integrity/digsig.c | 2 +- security/integrity/integrity.h | 6 +++++ .../integrity/platform_certs/platform_cert.S | 23 ++++++++++++++++ .../platform_certs/platform_keyring.c | 26 +++++++++++++++++++ 12 files changed, 91 insertions(+), 15 deletions(-)delete mode 100644
certs/common.h
create mode 100644security/integrity/platform_certs/platform_cert.Scerts/Makefile +2
-1@@ -3,7 +3,8 @@ # Makefile for the linux kernel signature checking certificates. # -obj-$(CONFIG_SYSTEM_TRUSTED_KEYRING) += system_keyring.o system_certificates.o common.o +obj-$(CONFIG_KEYS) += common.o +obj-$(CONFIG_SYSTEM_TRUSTED_KEYRING) += system_keyring.o system_certificates.o obj-$(CONFIG_SYSTEM_BLACKLIST_KEYRING) += blacklist.o common.o obj-$(CONFIG_SYSTEM_REVOCATION_LIST) += revocation_certificates.o ifneq ($(CONFIG_SYSTEM_BLACKLIST_HASH_LIST),"")certs/blacklist.c +0
-1@@ -17,7 +17,6 @@#include <linux/uidgid.h> #include <keys/system_keyring.h> #include "blacklist.h" -#include "common.h" static struct key *blacklist_keyring;certs/common.c +1
-1@@ -2,7 +2,7 @@#include <linux/kernel.h> #include <linux/key.h> -#include "common.h" +#include <keys/system_keyring.h> int load_certificate_list(const u8 cert_list[], const unsigned long list_size,certs/common.h deleted +0
-9@@ -1,9 +0,0 @@ -/* SPDX-License-Identifier: GPL-2.0-or-later */ - -#ifndef _CERT_COMMON_H -#define _CERT_COMMON_H - -int load_certificate_list (const u8 cert_list[],const unsigned long list_size, -const struct key *keyring); - -#endif certs/system_keyring.c +0
-1@@ -16,7 +16,6 @@#include <keys/asymmetric-type.h> #include <keys/system_keyring.h> #include <crypto/pkcs7.h> -#include "common.h" static struct key *builtin_trusted_keys;#ifdef CONFIG_SECONDARY_TRUSTED_KEYRING include/keys/system_keyring.h +6
-0@@ -10,6 +10,12 @@#include <linux/key.h> +#ifdef CONFIG_KEYS +int load_certificate_list (const u8 cert_list[], +const unsigned long list_size, +const struct key *keyring); +#endif +#ifdef CONFIG_SYSTEM_TRUSTED_KEYRING extern int restrict_link_by_builtin_trusted(struct key *keyring,security/integrity/Kconfig +10
-0@@ -62,6 +62,16 @@ config INTEGRITY_PLATFORM_KEYRING provided by the platform for verifying the kexec'ed kerned image and, possibly, the initramfs signature. +config INTEGRITY_PLATFORM_BUILTIN_KEYS + string "Builtin X.509 keys for .platform keyring" + depends on KEYS + depends on ASYMMETRIC_KEY_TYPE + depends on INTEGRITY_PLATFORM_KEYRING + help + If set, this option should be the filename of a PEM-formatted file + containing X.509 certificates to be loaded onto the ".platform" + keyring. + config LOAD_UEFI_KEYS depends on INTEGRITY_PLATFORM_KEYRING depends on EFIsecurity/integrity/Makefile +16
-1@@ -3,13 +3,18 @@ # Makefile for caching inode integrity data (iint) # +quiet_cmd_extract_certs = EXTRACT_CERTS $(patsubst "%",%,$(2)) + cmd_extract_certs = scripts/extract-cert $(2) $@ +$(eval $(call config_filename,INTEGRITY_PLATFORM_BUILTIN_KEYS)) + obj-$(CONFIG_INTEGRITY) += integrity.o integrity-y := iint.o integrity-$(CONFIG_INTEGRITY_AUDIT) += integrity_audit.o integrity-$(CONFIG_INTEGRITY_SIGNATURE) += digsig.o integrity-$(CONFIG_INTEGRITY_ASYMMETRIC_KEYS) += digsig_asymmetric.o -integrity-$(CONFIG_INTEGRITY_PLATFORM_KEYRING) += platform_certs/platform_keyring.o +integrity-$(CONFIG_INTEGRITY_PLATFORM_KEYRING) += platform_certs/platform_keyring.o \ + platform_certs/platform_cert.o integrity-$(CONFIG_LOAD_UEFI_KEYS) += platform_certs/efi_parser.o \ platform_certs/load_uefi.o \ platform_certs/keyring_handler.o@@ -19,3 +24,13 @@ integrity-$(CONFIG_LOAD_PPC_KEYS) += platform_certs/efi_parser.o \ platform_certs/keyring_handler.o obj-$(CONFIG_IMA) += ima/ obj-$(CONFIG_EVM) += evm/ + + +$(obj)/platform_certs/platform_cert.o: $(obj)/platform_certs/platform_certificate_list + +targets += platform_certificate_list + +$(obj)/platform_certs/platform_certificate_list: scripts/extract-cert $(INTEGRITY_PLATFORM_BUILTIN_KEYS_FILENAME) FORCE + $(call if_changed,extract_certs,$(CONFIG_INTEGRITY_PLATFORM_BUILTIN_KEYS)) + +clean-files := platform_certs/platform_certificate_listsecurity/integrity/digsig.c +1
-1@@ -38,7 +38,7 @@ static const char * const keyring_name[INTEGRITY_KEYRING_MAX] = {#define restrict_link_to_ima restrict_link_by_builtin_trusted#endif -static struct key *integrity_keyring_from_id (const unsigned int id) +struct key *integrity_keyring_from_id (const unsigned int id) {if (id >=INTEGRITY_KEYRING_MAX )return ERR_PTR (-EINVAL );security/integrity/integrity.h +6
-0@@ -167,6 +167,7 @@ int __init integrity_init_keyring(const unsigned int id);int __init integrity_load_x509 (const unsigned int id,const char *path);int __init integrity_load_cert (const unsigned int id,const char *source,const void *data,size_t len,key_perm_t perm); +struct key *integrity_keyring_from_id (const unsigned int id);#else static inline int integrity_digsig_verify(const unsigned int id,@@ -194,6 +195,11 @@ static inline int __init integrity_load_cert(const unsigned int id, {return 0 ; } + +static inline struct key *integrity_keyring_from_id (const unsigned int id) +{ +return ERR_PTR (-EOPNOTSUPP ); +}#endif /* CONFIG_INTEGRITY_SIGNATURE */ #ifdef CONFIG_INTEGRITY_ASYMMETRIC_KEYS security/integrity/platform_certs/platform_cert.S new file +0
-0security/integrity/platform_certs/platform_cert.S line 1
Quoted 1 line
security/integrity/platform_certs/platform_cert.S new file +1
-0@@ -0,0 +1,23 @@ +/* SPDX-License-Identifier: GPL-2.0 */My personal preference would be to have
platform_cert.Snext to all the other "extract certs and build an object out of them", as in /certs/platform_cert.S right next to the other similar .S files, i.esystem_certificates.Sandrevocation_certificates.Sit would make it easier to inspect the build and find all the various types of built-in keys.
Quoted 1 line
This is a minor comment/suggestion, that you can reject.
I think anything platform related should be in the platform_certs/ directory.
Quoted 51 lines
Quoted 41 lines
security/integrity/platform_certs/platform_cert.S new file +22
-0+#include <linux/export.h> +#include <linux/init.h> + + __INITRODATA + + .align 8 +#ifdef CONFIG_INTEGRITY_PLATFORM_KEYRING + .globl platform_certificate_list +platform_certificate_list: +__cert_list_start: + .incbin "security/integrity/platform_certs/platform_certificate_list" +__cert_list_end: +#endif + + .align 8 + .globl platform_certificate_list_size +platform_certificate_list_size: +#ifdef CONFIG_64BIT + .quad __cert_list_end - __cert_list_start +#else + .long __cert_list_end - __cert_list_start +#endifsecurity/integrity/platform_certs/platform_keyring.c +4
-0@@ -12,8 +12,12 @@#include <linux/cred.h> #include <linux/err.h> #include <linux/slab.h> +#include <keys/system_keyring.h> #include "../integrity.h" +extern __initconst const u8 platform_certificate_list[]; +extern __initconst const unsigned long platform_certificate_list_size; +/** * add_to_platform_keyring - Add to platform keyring without validation. * @source: Source of key security/integrity/platform_certs/platform_keyring.c void __init add_to_platform_keyring(const char *source, const void *data, · line 43
Quoted 3 lines
security/integrity/platform_certs/platform_keyring.c +0
-0@@ -37,6 +41,28 @@ void __init add_to_platform_keyring(const char *source, const void *data,pr_info ("Error adding keys to platform keyring %s\n" , source); }I think the below hunk should be guarded with #ifdef
CONFIG_INTEGRITY_PLATFORM_BUILTIN_KEYS, similar to how similar call is ifdef'ed in case of revocation keys i.e. see ifdefCONFIG_SYSTEM_REVOCATION_LISTincerts/blacklist.c. Because one can configure a kernel with a platform keyring, but without platform builtin keys.
Quoted 1 line
I think this must be be fixed.
If there are no builtin keys configured, then size would be zero and load_certificate_list would just return. I am not sure why it had to be ifdef'ed for revocation, I do not see the same for loading system certificates onto system keyring. Please let me know if you think I am missing something.
Quoted 34 lines
Quoted 13 lines
security/integrity/platform_certs/platform_keyring.c +12
-0+static __init int load_builtin_platform_cert (void ) +{ +const u8 *p; +unsigned long size; +int rc; +struct key *keyring; + + p = platform_certificate_list; + size = platform_certificate_list_size; + + keyring =integrity_keyring_from_id (INTEGRITY_KEYRING_PLATFORM ); +if (IS_ERR (keyring))security/integrity/platform_certs/platform_keyring.c void __init add_to_platform_keyring(const char *source, const void *data, · line 65
Quoted 10 lines
security/integrity/platform_certs/platform_keyring.c +10
-0+return PTR_ERR (keyring); + + rc =load_certificate_list (p, size, keyring); +if (rc) +pr_info ("Error adding keys to platform keyring %d\n" , rc); + +return rc; +} +late_initcall (load_builtin_platform_cert); +Some more general comment:
I do wonder if the refactor ofload_certificate_listcan be somehow avoided. For example, when platform keyring is allocated it callsset_platform_trusted_keys()fromcerts/system-keyring.cwhich could add a call toload_builtin_platform_cert, and it already has a handle to the platform keyring. Theset_platform_trusted_keys()could call toload_certificate_listthere withoutlate_initcall, alocating variables, and looking up theintegrity_keyring_fromid. It would make this feature patch very concise and straight forward then.
Quoted 8 lines
That way builtin platform certs will be done before platform specific load_*.c things are done. But also it will make builtin certs loading be done in a different place from the rest of the platform certs loading (e.g. the uefi one). So maybe doing builtin certs loading, next to all other platform cert loading makes sense, despite it being away from other builtin certs loading into other keyrings.
I am divided on this =)
Yes, I had also thought about it. I saw that set_platform_trusted_keys() call is dependent on CONFIG_SYSTEM_TRUSTED_KEYRING. By design, it should be possible to load platform certs onto the platform keyring even when the system keyring is not enabled. So, I preferred to keep it separate and in platform_keyring.c.
Thanks & Regards,
- Nayna