<feed xmlns='http://www.w3.org/2005/Atom'>
<title>efi-boot-shim.git/include, branch vyos/current</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=vyos%2Fcurrent</id>
<link rel='self' href='https://git.amelek.net/vyos/efi-boot-shim.git/atom?h=vyos%2Fcurrent'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/'/>
<updated>2025-03-14T15:05:05+00:00</updated>
<entry>
<title>Make 'make fanalyzer' work again.</title>
<updated>2025-03-14T15:05:05+00:00</updated>
<author>
<name>Peter Jones</name>
<email>pjones@redhat.com</email>
</author>
<published>2025-03-12T20:28:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=db1f1dac7e7f49b985d1c338c667c34424cb8d54'/>
<id>urn:sha1:db1f1dac7e7f49b985d1c338c667c34424cb8d54</id>
<content type='text'>
It breaks every time somehow.

Signed-off-by: Peter Jones &lt;pjones@redhat.com&gt;
</content>
</entry>
<entry>
<title>Some save_logs() improvements.</title>
<updated>2025-02-26T14:39:46+00:00</updated>
<author>
<name>Peter Jones</name>
<email>pjones@redhat.com</email>
</author>
<published>2025-02-25T19:33:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=9c423e09cd9a0196888253b16fe7022deadc20fc'/>
<id>urn:sha1:9c423e09cd9a0196888253b16fe7022deadc20fc</id>
<content type='text'>
In d972515e608e ("Save the debug and error logs in mok-variables") had a
few deficiencies: 1) the size of the result table isn't correctly
computed when either errlog or dbglog is 0 sized (much more likely for
the former), 2) when we save the error log we leak the allocation for
the previous mok variables, and 3) original mok variables were allocated
with AllocatePages(), but the new ones were allocated with
AllocateZeroPool().  The former guarantees page alignment, which we want
here.

This fixes all three of these.

Signed-off-by: Peter Jones &lt;pjones@redhat.com&gt;
</content>
</entry>
<entry>
<title>peimage.h: minor whitespace fixes</title>
<updated>2025-02-26T00:40:54+00:00</updated>
<author>
<name>Peter Jones</name>
<email>pjones@redhat.com</email>
</author>
<published>2025-02-25T14:00:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=c5c5287b8a0da20b711601921dc34a9cfa2e39db'/>
<id>urn:sha1:c5c5287b8a0da20b711601921dc34a9cfa2e39db</id>
<content type='text'>
Signed-off-by: Peter Jones &lt;pjones@redhat.com&gt;
</content>
</entry>
<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>pe: read_header(): allow skipping SecDir content validation</title>
<updated>2025-02-26T00:40:54+00:00</updated>
<author>
<name>Peter Jones</name>
<email>pjones@redhat.com</email>
</author>
<published>2025-02-25T16:44:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=3bce11831343ba6e67740f23ab3a6c6f09bc0bca'/>
<id>urn:sha1:3bce11831343ba6e67740f23ab3a6c6f09bc0bca</id>
<content type='text'>
When we're parsing the PE header of shim itself from the Loaded Image
object, the signatures aren't present, but the Certificate Table entry
in the Data Directory has not been cleared, so it'll fail verification.

We know when we're doing that, so this patch makes that test optional.

Signed-off-by: Peter Jones &lt;pjones@redhat.com&gt;
</content>
</entry>
<entry>
<title>HSI: Add decode_hsi_bits() for easier reading of the debug log</title>
<updated>2025-02-26T00:40:54+00:00</updated>
<author>
<name>Peter Jones</name>
<email>pjones@redhat.com</email>
</author>
<published>2025-02-25T15:41:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=1baf1efb37e2728104765477b12b70aeef3090af'/>
<id>urn:sha1:1baf1efb37e2728104765477b12b70aeef3090af</id>
<content type='text'>
This changes all the HSI bitfield operations to print a string showing
the change instead of just hex values.

Signed-off-by: Peter Jones &lt;pjones@redhat.com&gt;
</content>
</entry>
<entry>
<title>hexdump: give a different debug log for size==0</title>
<updated>2025-02-26T00:40:54+00:00</updated>
<author>
<name>Peter Jones</name>
<email>pjones@redhat.com</email>
</author>
<published>2025-02-24T17:00:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=c868d54def8cebd151964fdeaa8257932b8cfc39'/>
<id>urn:sha1:c868d54def8cebd151964fdeaa8257932b8cfc39</id>
<content type='text'>
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>Add support for DXE memory attribute updates.</title>
<updated>2025-02-24T20:58:16+00:00</updated>
<author>
<name>Peter Jones</name>
<email>pjones@redhat.com</email>
</author>
<published>2024-06-27T19:19:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=c41b1f066b9f279b70d933095f277eddbd7c6433'/>
<id>urn:sha1:c41b1f066b9f279b70d933095f277eddbd7c6433</id>
<content type='text'>
This adds DXE implementations of get_mem_attrs() and update_mem_attrs()
for machines that implement DXE but don't yet have the
EFI_MEMORY_ATTRIBUTE_PROTOCOL.

Signed-off-by: Peter Jones &lt;pjones@redhat.com&gt;
</content>
</entry>
<entry>
<title>Move mok state variable data flag definitions to the header.</title>
<updated>2025-02-24T20:26:20+00:00</updated>
<author>
<name>Peter Jones</name>
<email>pjones@redhat.com</email>
</author>
<published>2025-02-18T20:10:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=b216543d691050d6cdd37c3500571cf67882f1bc'/>
<id>urn:sha1:b216543d691050d6cdd37c3500571cf67882f1bc</id>
<content type='text'>
Previously the mok mirror state flags were only used in the mok
mirroring code.  But there are other consumers of that data, namely our
variable test cases, and it's useful for them to be able to check the
flags.

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