<feed xmlns='http://www.w3.org/2005/Atom'>
<title>efi-boot-shim.git/include, branch 15.4</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.4</id>
<link rel='self' href='https://git.amelek.net/vyos/efi-boot-shim.git/atom?h=15.4'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/'/>
<updated>2021-03-27T22:48:04+00:00</updated>
<entry>
<title>Change SBAT variable name to SbatLevel</title>
<updated>2021-03-27T22:48:04+00:00</updated>
<author>
<name>Jan Setje-Eilers</name>
<email>jan.setjeeilers@oracle.com</email>
</author>
<published>2021-03-27T18:09:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=27da4170f0fb30acde91a37e0256dfcfe76ea69e'/>
<id>urn:sha1:27da4170f0fb30acde91a37e0256dfcfe76ea69e</id>
<content type='text'>
Because a few shim builds were signed that did not properly initialize
the SBAT variable, and in doing so deleted valid SBAT variables, we need
to use a different name.

This changes the name from "SBAT" to "SbatLevel".

Signed-off-by: Jan Setje-Eilers &lt;jan.setjeeilers@oracle.com&gt;
</content>
</entry>
<entry>
<title>Move the check for the SBAT variable properties to its own function.</title>
<updated>2021-03-27T22:47:31+00:00</updated>
<author>
<name>Jan Setje-Eilers</name>
<email>jan.setjeeilers@oracle.com</email>
</author>
<published>2021-03-27T04:19:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=08a0ce01dbe9945287f37a9b139b25f46c53f878'/>
<id>urn:sha1:08a0ce01dbe9945287f37a9b139b25f46c53f878</id>
<content type='text'>
This moves the check for the SBAT variable's attributes and contents
into its own function, so that test cases can be written against it.

Signed-off-by: Jan Setje-Eilers &lt;jan.setjeeilers@oracle.com&gt;
</content>
</entry>
<entry>
<title>Make 'make test' work on gcc 4.8.5</title>
<updated>2021-03-22T20:43:44+00:00</updated>
<author>
<name>Peter Jones</name>
<email>pjones@redhat.com</email>
</author>
<published>2021-03-21T19:57:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=33db42def2ce6fe040b5f77642347e8b3c6420e5'/>
<id>urn:sha1:33db42def2ce6fe040b5f77642347e8b3c6420e5</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Ensure that MOK variable mirroring creates well formed ESLs</title>
<updated>2021-03-19T02:47:43+00:00</updated>
<author>
<name>Chris Coulson</name>
<email>chris.coulson@canonical.com</email>
</author>
<published>2021-03-18T14:32:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=3dd40ade68c6ff63e776b5f9acbd811a3c345d01'/>
<id>urn:sha1:3dd40ade68c6ff63e776b5f9acbd811a3c345d01</id>
<content type='text'>
The MOK variable mirroring makes use of variable_create_esl, which
can only create a well-formed EFI_SIGNATURE_LIST containing a single
signature. Fix fill_esl and variable_create_esl to support creating
a EFI_SIGNATURE_LIST with one or more supplied EFI_SIGNATURE_DATA
structures.

Introduce variable_create_esl_with_one_signature and
fill_esl_with_one_signature for code that does want to create a
EFI_SIGNATURE_LIST containing a single signature constructed from
a supplied signature data buffer and owner GUID.
</content>
</entry>
<entry>
<title>Fix up build of test code using gcc 8</title>
<updated>2021-03-15T23:52:17+00:00</updated>
<author>
<name>Steve McIntyre</name>
<email>steve@einval.com</email>
</author>
<published>2021-03-15T23:12:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=f5a3de3264f87f48186f80297fb1dbcddfd6d945'/>
<id>urn:sha1:f5a3de3264f87f48186f80297fb1dbcddfd6d945</id>
<content type='text'>
Don't check SHIM_UNIT_TEST.

This fixes conflicting declarations for __builtin_ms_va_list on amd64:

In file included from shim.h:47,
                 from test.c:10:
../include/system/stdarg.h:30:27: error: conflicting types for '__builtin_ms_va_list'
 typedef __builtin_va_list __builtin_ms_va_list;
                           ^~~~~~~~~~~~~~~~~~~~
cc1: note: previous declaration of '__builtin_ms_va_list' was here
In file included from shim.h:47,
                 from test-csv.c:9:
../include/system/stdarg.h:30:27: error: conflicting types for '__builtin_ms_va_list'
 typedef __builtin_va_list __builtin_ms_va_list;
                           ^~~~~~~~~~~~~~~~~~~~
cc1: note: previous declaration of '__builtin_ms_va_list' was here
In file included from shim.h:47,
                 from csv.c:6:
../include/system/stdarg.h:30:27: error: conflicting types for '__builtin_ms_va_list'
 typedef __builtin_va_list __builtin_ms_va_list;
                           ^~~~~~~~~~~~~~~~~~~~
cc1: note: previous declaration of '__builtin_ms_va_list' was here

Signed-off-by: Steve McIntyre &lt;93sam@debian.org&gt;
</content>
</entry>
<entry>
<title>'make test': try harder to make it build in the right order.</title>
<updated>2021-03-12T09:15:01+00:00</updated>
<author>
<name>Peter Jones</name>
<email>pjones@redhat.com</email>
</author>
<published>2021-03-12T02:56:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=39b96c01bfd4547f38c9e573ff5d551057ea272c'/>
<id>urn:sha1:39b96c01bfd4547f38c9e573ff5d551057ea272c</id>
<content type='text'>
Signed-off-by: Peter Jones &lt;pjones@redhat.com&gt;
</content>
</entry>
<entry>
<title>sbat variable: use UEFI_VAR_NV_BS_RT when we've got ENABLE_SHIM_DEVEL</title>
<updated>2021-03-12T09:15:01+00:00</updated>
<author>
<name>Peter Jones</name>
<email>pjones@redhat.com</email>
</author>
<published>2021-03-11T22:19:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=76f35c00ef9df3958c5479d74f8d6605c32901ec'/>
<id>urn:sha1:76f35c00ef9df3958c5479d74f8d6605c32901ec</id>
<content type='text'>
This makes it so that if you build with ENABLE_SHIM_DEVEL, the SBAT we
use is named SBAT_DEVEL instead of SBAT, and it's expected to have
EFI_VARIABLE_RUNTIME_ACCESS set.

Signed-off-by: Peter Jones &lt;pjones@redhat.com&gt;
</content>
</entry>
<entry>
<title>Don't even try to use builtins, just make sure we have the same types.</title>
<updated>2021-03-12T09:15:01+00:00</updated>
<author>
<name>Peter Jones</name>
<email>pjones@redhat.com</email>
</author>
<published>2021-03-12T01:07:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=b5a7c8ce6012ec8d5f9f2515537f918ef4ca9358'/>
<id>urn:sha1:b5a7c8ce6012ec8d5f9f2515537f918ef4ca9358</id>
<content type='text'>
For some reason when we try to ever use the builtins, even with the
symbol there as a fallback, something goes horribly wrong somewhere
around here:

| (gdb) bt
| #0  strcmp (s1=0x7d492359 "MD5", s2=0x7d492359 "MD5") at include/system/string.h:57
| #1  0x000000007d460419 in getrn (lh=lh@entry=0x7e081318, data=data@entry=0x7e084398, rhash=rhash@entry=0x7f7c9268) at crypto/lhash/lhash.c:415
| #2  0x000000007d46076e in lh_insert (lh=0x7e081318, data=data@entry=0x7e084398) at crypto/lhash/lhash.c:188
| #3  0x000000007d43e027 in OBJ_NAME_add (name=name@entry=0x7d492359 "MD5", type=type@entry=1, data=data@entry=0x7d4ad3a0 &lt;md5_md&gt; "\004") at crypto/objects/o_names.c:202

As much as I love a Sisyphean challenge, in the interest of not having
bugs or time, this patch changes it to just not use them for anything
other than guaranteeing our implementations have the exact same types as
you would expect.

Signed-off-by: Peter Jones &lt;pjones@redhat.com&gt;
</content>
</entry>
<entry>
<title>More va_* work</title>
<updated>2021-03-12T09:15:01+00:00</updated>
<author>
<name>Peter Jones</name>
<email>pjones@redhat.com</email>
</author>
<published>2021-03-11T21:48:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=4457d79ce0ea638e7732f5529bf13849e290940d'/>
<id>urn:sha1:4457d79ce0ea638e7732f5529bf13849e290940d</id>
<content type='text'>
Be much more explicit about exactly which va_* stuff comes from which
ABI in both shim and gnu-efi.  This fixes the problem where we see:

| (null):0:(null)() v-&gt;name:"(null)" v-&gt;rtname:"(null)"
| (null):0:(null)() v-&gt;data_size:0 v-&gt;data:0x0

and similar messages where everything is NULL.

Signed-off-by: Peter Jones &lt;pjones@redhat.com&gt;
</content>
</entry>
<entry>
<title>Fix the compiler when invoking scan-build/fanalyzer/etc</title>
<updated>2021-03-12T09:15:01+00:00</updated>
<author>
<name>Peter Jones</name>
<email>pjones@redhat.com</email>
</author>
<published>2021-03-11T16:40:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=6ebae16cbb6856f80e891b710d4f76b49ff48c6d'/>
<id>urn:sha1:6ebae16cbb6856f80e891b710d4f76b49ff48c6d</id>
<content type='text'>
Signed-off-by: Peter Jones &lt;pjones@redhat.com&gt;
</content>
</entry>
</feed>
