On 7 September 2017 at 16:24, Thiebaud Weksteen wrote:
> Hi Ard,
>
> Thanks for reviewing the patch. (Non-addressed comments are fixed in the
> next patch set).
>
> On Wed, Sep 06, 2017 at 03:53:33PM +0100, Ard Biesheuvel wrote:
>> Hi Thiebaud,
>>
>> On 6 September 2017 at 15:25, Thiebaud Weksteen
Hi Ard,
Thanks for reviewing the patch. (Non-addressed comments are fixed in the
next patch set).
On Wed, Sep 06, 2017 at 03:53:33PM +0100, Ard Biesheuvel wrote:
> Hi Thiebaud,
>
> On 6 September 2017 at 15:25, Thiebaud Weksteen wrote:
> > With TPM 2.0, access to the event log is only possible
On 6 September 2017 at 15:53, Ard Biesheuvel wrote:
> Hi Thiebaud,
>
> On 6 September 2017 at 15:25, Thiebaud Weksteen wrote:
>> With TPM 2.0, access to the event log is only possible by using the
>> EFI TPM2 Boot Service. Modify the EFI stub to copy the log area to a new
>> Linux-specific EFI ta
Hi Thiebaud,
On 6 September 2017 at 15:25, Thiebaud Weksteen wrote:
> With TPM 2.0, access to the event log is only possible by using the
> EFI TPM2 Boot Service. Modify the EFI stub to copy the log area to a new
> Linux-specific EFI table so it remains accessible for future use.
>
> Signed-off-b
With TPM 2.0, access to the event log is only possible by using the
EFI TPM2 Boot Service. Modify the EFI stub to copy the log area to a new
Linux-specific EFI table so it remains accessible for future use.
Signed-off-by: Thiebaud Weksteen
---
arch/x86/boot/compressed/eboot.c | 1 +
driver
