linux-kernel - Re: [PATCH v3 4/5] efi: call get_event

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LRH.2.21.1710111250260.22885@namei.org>
Date:   Wed, 11 Oct 2017 12:54:26 +1100 (AEDT)
From:   James Morris <jmorris@...ei.org>
To:     Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
cc:     Thiebaud Weksteen <tweek@...gle.com>, linux-efi@...r.kernel.org,
        linux-integrity@...r.kernel.org, tpmdd-devel@...ts.sourceforge.net,
        Ard Biesheuvel <ard.biesheuvel@...aro.org>,
        Matt Fleming <matt@...eblueprint.co.uk>,
        linux-kernel@...r.kernel.org, Matthew Garrett <mjg59@...gle.com>,
        peterhuewe@....de,
        Jason Gunthorpe <jgunthorpe@...idianresearch.com>,
        tpmdd@...horst.net
Subject: Re: [PATCH v3 4/5] efi: call get_event_log before ExitBootServices

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@...ei.org>