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@xxxxxxxxx> > > > > 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 -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
