-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 pjones' statement about Secure Boot on 2022-05-02: I'm involved in Secure Boot signing in various distros in several ways. I wrote and maintain pesign ( https://github.com/rhinstaller/pesign ), which is used for signing EFI binaries, and I'm one of the upstream maintainers of shim ( https://github.com/rhinstaller/shim ), which most Linux distros use to transition from the firmware's security domain to the kernel's. I'm also responsible for Fedora and RHEL's builds of pesign, shim, and grub2. I'm not responsible for the kernels for RHEL or Fedora, nor for determining which of them finally get signed for Secure Boot. I have been responsible for generating keys for signing Fedora's binaries. As the guy who gets shim signed for Fedora: At no point have I been contacted with warrants of any kind, or any similar instrument, or in any way, from governmental or non-governmental entities, about inclusion of any kind of malware or backdoor in Fedora's signed secure boot binaries, including shim, grub2, the kernel, and pesign, nor have I at any time been approached about disclosure of our signing keys, except by one lazy troll on the internet. I am also not aware of anyone else involved in our signing that has been contacted with warrants of any kind, or any similar instrument, or in any way, from governmental or non-governmental entities, about inclusion of any kind of malware or backdoor in Fedora's signed secure boot binaries, including shim, grub2, the kernel, and pesign, nor am I aware of any other involved party having at any time been approached about disclosure of our signing keys. As the guy who gets shim signed for RHEL: At no point have I been contacted with warrants of any kind, or any similar instrument, or in any way, from governmental or non-governmental entities, about inclusion of any kind of malware or backdoor in RHEL's signed secure boot binaries, including shim, grub2, the kernel, and pesign, nor have I at any time been approached about disclosure of our signing keys. I am also not aware of anyone else involved in our signing that has been contacted with warrants of any kind, or any similar instrument, or in any way, from governmental or non-governmental entities, about inclusion of any kind of malware or backdoor in RHEL's signed secure boot binaries, including shim, grub2, the kernel, and pesign, nor am I aware of any other involved party having at any time been approached about disclosure of our signing keys. As a person involved in CentOS implementation in an advisory role: I am not aware of anyone else involved in our signing that has been contacted with warrants of any kind, or any similar instrument, or in any way, from governmental or non-governmental entities, about inclusion of any kind of malware or backdoor in CentOS's signed secure boot binaries, including shim, grub2, the kernel, and pesign, nor am I aware of any other involved party having at any time been approached about disclosure of CentOS's signing keys. As the guy who gets shim signed for CentOS: At no point have I been contacted with warrants of any kind, or any similar instrument, or in any way, from governmental or non-governmental entities, about inclusion of any kind of malware or backdoor in RHEL's signed secure boot binaries, including shim, grub2, the kernel, and pesign, nor have I at any time been approached about disclosure of our signing keys. I am also not aware of anyone else involved in our signing that has been contacted with warrants of any kind, or any similar instrument, or in any way, from governmental or non-governmental entities, about inclusion of any kind of malware or backdoor in CentOS 7's signed secure boot binaries, including shim, grub2, the kernel, and pesign, nor am I aware of any other involved party having at any time been approached about disclosure of our signing keys. As the upstream maintainer of pesign and an upstream maintainer of shim: At no point have I been contacted with warrants of any kind, or any similar instrument, or in any way, from governmental or non-governmental entities, about inclusion of any kind of malware or backdoor into either shim or pesign. I am also unaware of any other contributor to shim or pesign having been contacted with warrants of of any kind, or any similar instrument, or in any way, from governmental or non-governmental entities, about inclusion of any kind of malware or backdoor into either shim or pesign. November 2017 update: One rando from the internet has sent me an email to tell me that I should "consider myself approached" regarding the Fedora signing keys. Here's what the guy with way too much time on his hands said: - ------------------------------------------------------------------------------ Date: Tue, 31 Oct 2017 14:46:07 -0400 From: Eduardo Gines Subject: Fedora SecureBoot signing keys Hey Peter, I'd like you to share with me key used for signing shim in Fedora Project Linux. Consider yourself approached. Adiós, Eduardo - ------------------------------------------------------------------------------ Just so we're clear, I don't consider a lazy email to be the sort of contact we're talking about here. So while I've changed the language on the Fedora section above to reflect that I have, in fact, been contacted in /some/ way by a non-governmental entity, in the future if this is the amount of effort you put into this, I'm just going to mark it spam. Congratulations, you found a new way to be bad for the world, and it's mostly just tedious. Most people just stick to the old ways. September 2018 update: Changed some CentOS stuff around to better reflect the current division of labor. March 2021 update: There's been some discussion about some documents published by the National Security Agency[0]. In these, they discuss deployment strategies and customizations regarding UEFI and Secure Boot. [0] Here: https://www.nsa.gov/Portals/70/documents/what-we-do/cybersecurity/professional-resources/csi-uefi-lockdown.pdf https://www.nsa.gov/Portals/70/documents/what-we-do/cybersecurity/professional-resources/BootSecurityModesAndRec_20190522.pdf https://media.defense.gov/2020/Sep/15/2002497594/-1/-1/0/CTR-UEFI-Secure-Boot-Customization-UOO168873-20.PDF https://github.com/nsacyber/Hardware-and-Firmware-Security-Guidance/blob/master/secureboot/Linux.md -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJib/ayAAoJEO7SZrcPT+8Q7ZYP/27TUBvBFbMXL2V13gNgSVsM cRd0RJ8DYoc6Gl38i6kkhe+nGluD+xQyDQ9z6PHrG6xBi+sWeNWYBM5PJBPpqppx CZzIt8alDvNXvZttr3y6EOe+oMNjlZZTKCte9dmZQKyrjvwYOn0Voq/HNNh5objZ IDLWaVvq+nXPBfyzLlZRKvJHBbiAjJB4tRVlXRTKeOsXPC4OmpZccWFCzmWML/50 iv1ujRDEaLNtgvEHh8tid+APdSwkznv5bvhQgaQci7seieo3BwJ3g7OUHldoPwZZ XhL1pEW+4W2FDxZCg3uVSlNgWzJPPu29mUtS9XUyMnGp76L6xm9BSJbuaHek38fc ZVnOk7OlTMrrnL8hgShUZTFIP2lstbMrAa4uzRj/ZXGeR96WILE6FM2NVYNXEPD5 Qs3REmIwxR/Yq9StitcbjXmEU5tN3ykkjo7sbV8g3HtKCSWIMI2w7NSa1EJyfwcG vsYZyb6tvGEyizidXSERTgJFqXr3Y0J2l4onFQRO3SdTj3tDvYPJNyQvmNXIqXOu RyN65ylK+ySF/FUD+cr5N6hniIHuQN5JaIVsXezue4nA8c7W1gThVOaKCgnc1ZrO s0paNlzTVX95gCBGGTBemEWy9M10P5HmdbmFSSEXRjfTL9IZ1mhGYF6K1iZCu6FE saTD81bfn9E3bX0n1cUQ =tAbM -----END PGP SIGNATURE-----