<feed xmlns='http://www.w3.org/2005/Atom'>
<title>efi-boot-shim.git/include/test-data-efivars-1.h, branch rolling</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=rolling</id>
<link rel='self' href='https://git.amelek.net/vyos/efi-boot-shim.git/atom?h=rolling'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/'/>
<updated>2025-02-26T00:40:54+00:00</updated>
<entry>
<title>Add shim's current NX_COMPAT status to HSIStatus</title>
<updated>2025-02-26T00:40:54+00:00</updated>
<author>
<name>Peter Jones</name>
<email>pjones@redhat.com</email>
</author>
<published>2025-02-21T00:20:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=89e615081af5fbafefeae5b09def3a003e467838'/>
<id>urn:sha1:89e615081af5fbafefeae5b09def3a003e467838</id>
<content type='text'>
hughsie asked me to also make it observable at runtime whether the shim
binary that was used to boot was set as NX_COMPAT or not.

This adds that into the HSIStatus data as "shim-has-nx-compat-set".

Signed-off-by: Peter Jones &lt;pjones@redhat.com&gt;
</content>
</entry>
<entry>
<title>Add DXE Services information to HSI</title>
<updated>2025-02-24T20:58:16+00:00</updated>
<author>
<name>Peter Jones</name>
<email>pjones@redhat.com</email>
</author>
<published>2025-02-20T19:44:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=9269e9b0aa15ae9832f7eba6c5eeef0c5e1f4edb'/>
<id>urn:sha1:9269e9b0aa15ae9832f7eba6c5eeef0c5e1f4edb</id>
<content type='text'>
This adds three more entries to our HSI data:

has-dxe-services-table: technically only tells us if UEFI's
			LocateProtocol will give us a DXE services
			table, but practically also tells us if the
			machine is implementing DXE in any way.
has-get-memory-space-descriptor: tells us if DXE-&gt;GetMemorySpaceDescriptor
                                 is populated
has-set-memory-space-descriptor: tells us if DXE-&gt;SetMemorySpaceDescriptor
                                 is populated

Signed-off-by: Peter Jones &lt;pjones@redhat.com&gt;
</content>
</entry>
<entry>
<title>shim: add HSIStatus feature</title>
<updated>2025-02-24T20:24:24+00:00</updated>
<author>
<name>Peter Jones</name>
<email>pjones@redhat.com</email>
</author>
<published>2024-05-15T20:13:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=848667d0f3a99401d93c93b3af16b55e3fb28cea'/>
<id>urn:sha1:848667d0f3a99401d93c93b3af16b55e3fb28cea</id>
<content type='text'>
hughsie asked me if I can make shim tell userland what kinds of accesses
are allowed to the heap, stack, and allocations on the running platform,
so that these could be reported up through fwupd's Host Security ID
program (see https://fwupd.github.io/libfwupdplugin/hsi.html ).

This adds a new config-only (i.e. not a UEFI variable) variable
generated during boot, "/sys/firmware/efi/mok-variables/HSIStatus",
which tells us those properties as well as if the EFI Memory Attribute
Protocol is present.

Signed-off-by: Peter Jones &lt;pjones@redhat.com&gt;
</content>
</entry>
<entry>
<title>Allow MokListTrusted to be enabled by default</title>
<updated>2022-05-04T18:58:23+00:00</updated>
<author>
<name>Eric Snowberg</name>
<email>eric.snowberg@oracle.com</email>
</author>
<published>2022-02-17T23:29:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=2670c6a17edb239949152c471445fc533d8525aa'/>
<id>urn:sha1:2670c6a17edb239949152c471445fc533d8525aa</id>
<content type='text'>
Within previous versions of shim the MokListTrusted var did not
exist. The user had to opt in to using the feature.

Change the default behavior to an opt out model. Since old
shims will not have the BS MokListTrusted set, use inverse
logic that sets the MokListTrustedRT to 1 when the boot
service variable is missing.

Many Linux distros carry out of tree patches to trust the mok
keys by default.  These out of tree patches can be dropped
when using a Linux kernel that supports MokListTrustedRT.

Signed-off-by: Eric Snowberg &lt;eric.snowberg@oracle.com&gt;
</content>
</entry>
<entry>
<title>tests: Add a unit test for mok mirroring</title>
<updated>2021-09-07T21:05:04+00:00</updated>
<author>
<name>Peter Jones</name>
<email>pjones@redhat.com</email>
</author>
<published>2021-07-23T18:36:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=397f820b8c091ca5e3023b6dbd2f26fb256a19f0'/>
<id>urn:sha1:397f820b8c091ca5e3023b6dbd2f26fb256a19f0</id>
<content type='text'>
Test that our mok mirroring doesn't ever try to delete any variable that
it has previously created, and that it properly mirrors at least
MokList, MokListX, and SbatLevel, at least when variables actually work.

These tests will fail (rather a lot) without 7f64fd6da9458b73c4.

Currently valgrind shows a memory leak in this code which is not
introduced in this patch series.  Since all of our memory is freed on
Exit() or when kernel does ExitBootServices(), this doesn't have any
significant repercussions.

Signed-off-by: Peter Jones &lt;pjones@redhat.com&gt;
</content>
</entry>
</feed>
