lkml.org 
[lkml]   [2017]   [Oct]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v3 4/5] efi: call get_event_log before ExitBootServices
On Mon, Oct 16, 2017 at 02:28:33PM +0300, Jarkko Sakkinen wrote:
> On Wed, Oct 11, 2017 at 02:52:54PM +0300, Jarkko Sakkinen wrote:
> > On Wed, Oct 11, 2017 at 12:54:26PM +1100, James Morris wrote:
> > > On Tue, 10 Oct 2017, Jarkko Sakkinen wrote:
> > >
> > > > The way I've agreed with James Morris to have my tree is to be rooted to
> > > > security trees next branch.
> > > >
> > > > James, what actions should we take?
> > >
> > > This process has changed recently -- I posted to lsm but forgot to post to
> > > linux-integrity.
> > >
> > > http://kernsec.org/pipermail/linux-security-module-archive/2017-September/003356.html
> > >
> > > Summary: please track the next-general branch in my tree for your
> > > development, it replaces 'next'.
> > >
> > >
> > > - James
> > > --
> > > James Morris
> > > <jmorris@namei.org>
> >
> > Ah I'm subscribed to that list but lately been busy getting a huge patch
> > set to platform-driver-x86 [1] for review, which has prioritized out
> > reading much else than linux-integrity.
> >
> > Thank you. I'll retry the patches tomorrow.
> >
> > /Jarkko
>
> Cannot observer binary_bios_measuremens file.
>
> What kind of hardware was used to develop/test this?
>
> I tried it with Kabylake and PTT (firmware TPM).
>
> /Jarkko

My guess would be wrong event log format.

At minimum this patch set should add a klog (info level) message to tell
that unsupported event log format is being used.

/Jarkko

\
 
 \ /
  Last update: 2017-10-16 13:50    [W:0.125 / U:0.156 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site