<feed xmlns='http://www.w3.org/2005/Atom'>
<title>efi-boot-shim.git/include, branch 15.7</title>
<subtitle> (mirror of https://github.com/vyos/efi-boot-shim.git)
</subtitle>
<id>https://git.amelek.net/vyos/efi-boot-shim.git/atom?h=15.7</id>
<link rel='self' href='https://git.amelek.net/vyos/efi-boot-shim.git/atom?h=15.7'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/'/>
<updated>2022-11-16T21:35:47+00:00</updated>
<entry>
<title>Bump grub's sbat requirement to grub,3</title>
<updated>2022-11-16T21:35:47+00:00</updated>
<author>
<name>Peter Jones</name>
<email>pjones@redhat.com</email>
</author>
<published>2022-11-16T18:25:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=dd8be98cf0fceddd9f156d2917565b18d38c4830'/>
<id>urn:sha1:dd8be98cf0fceddd9f156d2917565b18d38c4830</id>
<content type='text'>
Due to the issues addressed in the 2022-11-15 batch of grub CVEs[0], we
need to bump the sbat version from grub.  This patch changes it from 2
to 3.

[0] https://lists.gnu.org/archive/html/grub-devel/2022-11/msg00059.html

Signed-off-by: Peter Jones &lt;pjones@redhat.com&gt;
</content>
</entry>
<entry>
<title>shim: Flush the memory region from i-cache before execution</title>
<updated>2022-10-04T17:53:11+00:00</updated>
<author>
<name>dann frazier</name>
<email>dann.frazier@canonical.com</email>
</author>
<published>2022-09-06T15:28:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=5c537b3d0cf8c393dad2e61d49aade68f3af1401'/>
<id>urn:sha1:5c537b3d0cf8c393dad2e61d49aade68f3af1401</id>
<content type='text'>
We've seen crashes in early GRUB code on an ARM Cortex-A72-based
platform that point at seemingly harmless instructions. Flushing
the i-cache of those instructions prior to executing has been
shown to avoid the problem, which has parallels with this story:
  https://www.mail-archive.com/osv-dev@googlegroups.com/msg06203.html

Add a cache flushing utility function and provide an implementation
using a GCC intrinsic. This will need to be extended to support other
compilers. Note that this intrinsic is a no-op for x86 platforms.

This fixes issue #498.

Signed-off-by: dann frazier &lt;dann.frazier@canonical.com&gt;
</content>
</entry>
<entry>
<title>Discard load-options that start with a NUL</title>
<updated>2022-09-01T19:38:02+00:00</updated>
<author>
<name>Robbie Harwood</name>
<email>rharwood@redhat.com</email>
</author>
<published>2022-08-23T16:07:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=14d63398298c8de23036a4cf61594108b7345863'/>
<id>urn:sha1:14d63398298c8de23036a4cf61594108b7345863</id>
<content type='text'>
In 6c8d08c0af4768c715b79c8ec25141d56e34f8b4 ("shim: Ignore UEFI
LoadOptions that are just NUL characters."), a check was added to
discard load options that are entirely NUL.  We now see some firmwares
that start LoadOptions with a NUL, and then follow it with garbage (path
to directory containing loaders).  Widen the check to just discard
anything that starts with a NUL.

Resolves: #490
Related: #95
See-also: https://bugzilla.redhat.com/show_bug.cgi?id=2113005
Signed-off-by: Robbie Harwood &lt;rharwood@redhat.com&gt;
</content>
</entry>
<entry>
<title>Enable TDX measurement to RTMR register</title>
<updated>2022-08-16T21:45:30+00:00</updated>
<author>
<name>Lu Ken</name>
<email>ken.lu@intel.com</email>
</author>
<published>2022-05-22T08:02:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=4fd484e4c29364b4fdf4d043556fa0a210c5fdfc'/>
<id>urn:sha1:4fd484e4c29364b4fdf4d043556fa0a210c5fdfc</id>
<content type='text'>
Intel Trust Domain Extensions (Intel TDX) extends Virtual Machine
Extensions (VMX) and Multi-Key Total Memory Encryption (MK-TME) with a
new kind of virtual machine guest called a Trust Domain(TD)[1].  A TD
runs in a CPU mode that is designed to protect the confidentiality of
its memory contents and its CPU state from any other software, including
the hosting Virtual Machine Monitor (VMM).

Trust Domain Virtual Firmware (TDVF) is required to provide Intel TDX
implementation and service for EFI_CC_MEASUREMENT_PROTOCOL[2]. The bugzilla
for TDVF is at https://bugzilla.tianocore.org/show_bug.cgi?id=3625.

To support CC measurement/attestation with Intel TDX technology, these 4
RTMR registers will be extended by TDX service like TPM/TPM2 PCR:

- RTMR[0] for TDVF configuration
- RTMR[1] for the TD OS loader and kernel
- RTMR[2] for the OS application
- RTMR[3] reserved for special usage only

Add a TDX Implementation for CC Measurement protocol along with
TPM/TPM2 protocol.

References:
[1] https://software.intel.com/content/dam/develop/external/us/en/documents/tdx-whitepaper-v4.pdf
[2] https://software.intel.com/content/dam/develop/external/us/en/documents/tdx-virtual-firmware-design-guide-rev-1.pdf
[3] https://software.intel.com/content/dam/develop/external/us/en/documents/intel-tdx-guest-hypervisor-communication-interface-1.0-344426-002.pdf

Signed-off-by: Lu Ken &lt;ken.lu@intel.com&gt;
[rharwood: style pass on code and commit message]
Signed-off-by: Robbie Harwood &lt;rharwood@redhat.com&gt;
</content>
</entry>
<entry>
<title>Make SBAT variable payload introspectable</title>
<updated>2022-08-03T18:54:57+00:00</updated>
<author>
<name>Chris Coulson</name>
<email>chris.coulson@canonical.com</email>
</author>
<published>2022-05-31T21:21:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=0eb07e11b20680200d3ce9c5bc59299121a75388'/>
<id>urn:sha1:0eb07e11b20680200d3ce9c5bc59299121a75388</id>
<content type='text'>
Given a set of EFI variables and boot assets, it should be possible
to compute what the value of PCR 7 will be on the next boot.

As shim manages the contents of the SbatLevel variable and this is
measured to PCR 7, export the payloads that shim contains in a new
COFF section (.sbatlevel) so that it can be introspected by code
outside of shim.

The new section works a bit like .vendor_cert - it contains a header
and then the payload. In this case, the header contains no size fields
because the strings are NULL terminated. Shim uses this new section
internally in set_sbat_uefi_variable.

The .sbatlevel section starts with a 4 byte version field which is
not used by shim but may be useful for external auditors if the
format of the section contents change in the future.

Signed-off-by: Chris Coulson &lt;chris.coulson@canonical.com&gt;
</content>
</entry>
<entry>
<title>Update SBAT generation requirements for 05/24/22</title>
<updated>2022-05-24T20:28:35+00:00</updated>
<author>
<name>Jan Setje-Eilers</name>
<email>jan.setjeeilers@oracle.com</email>
</author>
<published>2022-05-10T21:09:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=9a09faf390eea083c3bef1b07c7e043ebe0cc1f6'/>
<id>urn:sha1:9a09faf390eea083c3bef1b07c7e043ebe0cc1f6</id>
<content type='text'>
bump shim SBAT generation requirement to 2 for CVE-2022-28737
bump GRUB2 SBAT generation requirement to 2 for CVE-2021-3695

Signed-off-by: Jan Setje-Eilers &lt;jan.setjeeilers@oracle.com&gt;
</content>
</entry>
<entry>
<title>Give the Coverity scanner some more GCC blinders...</title>
<updated>2022-05-23T20:49:53+00:00</updated>
<author>
<name>Peter Jones</name>
<email>pjones@redhat.com</email>
</author>
<published>2022-05-19T19:55:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=aa61fdf490d16aaa23de0cbe5e9f16d3bc72e582'/>
<id>urn:sha1:aa61fdf490d16aaa23de0cbe5e9f16d3bc72e582</id>
<content type='text'>
Coverity complains:

  CID 373676 (#3 of 3): Unrecoverable parse warning (PARSE_ERROR)
  1. arguments_provided_for_attribute: attribute "__malloc__" does not take arguments

This is, of course, just plain wrong.  Even so, I'm tired of looking at
it, so this patch wraps the #define we use for that attribute in a check
to see if it's being built by Coverity.

Signed-off-by: Peter Jones &lt;pjones@redhat.com&gt;
</content>
</entry>
<entry>
<title>sbat policy: make our policy change actions symbolic</title>
<updated>2022-05-18T20:37:23+00:00</updated>
<author>
<name>Peter Jones</name>
<email>pjones@redhat.com</email>
</author>
<published>2022-05-18T19:14:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=a50d3645467fcfef970a00154d6d49494355afc9'/>
<id>urn:sha1:a50d3645467fcfef970a00154d6d49494355afc9</id>
<content type='text'>
There are a couple of places where the code we've got right now just
uses integers to decode one of our MoK variables.  That's bad.

This patch replaces those with symbolic names.

Signed-off-by: Peter Jones &lt;pjones@redhat.com&gt;
</content>
</entry>
<entry>
<title>peimage.h: make our signature macros force the type</title>
<updated>2022-05-18T20:37:23+00:00</updated>
<author>
<name>Peter Jones</name>
<email>pjones@redhat.com</email>
</author>
<published>2022-05-18T18:54:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=f28833f7cbb3f536081b19c8a2cc6f709e772128'/>
<id>urn:sha1:f28833f7cbb3f536081b19c8a2cc6f709e772128</id>
<content type='text'>
scan-build invoked clang in a way that complains about our
SIGNATURE_XX() macro's sizes being used to assign to things that are
that size in post-process-pe.c.

This patch makes them cast the results to the appropriately sized type.

Signed-off-by: Peter Jones &lt;pjones@redhat.com&gt;
</content>
</entry>
<entry>
<title>sbat.h: minor reformatting for legibility</title>
<updated>2022-05-18T20:37:23+00:00</updated>
<author>
<name>Peter Jones</name>
<email>pjones@redhat.com</email>
</author>
<published>2022-05-18T18:39:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=610a1ac7614d2ad97b81b250dc37643df610d4f5'/>
<id>urn:sha1:610a1ac7614d2ad97b81b250dc37643df610d4f5</id>
<content type='text'>
Signed-off-by: Peter Jones &lt;pjones@redhat.com&gt;
</content>
</entry>
</feed>
