linux-kernel - Re: [PATCH 03/27] Enforce module signatures if the kernel is locked down

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]

Date:   Sat, 9 Mar 2019 10:00:38 +1100 (AEDT)
From:   James Morris <jmorris@...ei.org>
To:     Matthew Garrett <matthewgarrett@...gle.com>
cc:     linux-security-module@...r.kernel.org,
        linux-kernel@...r.kernel.org, dhowells@...hat.com
Subject: Re: [PATCH 03/27] Enforce module signatures if the kernel is locked
 down

On Wed, 6 Mar 2019, Matthew Garrett wrote:

> From: David Howells <dhowells@...hat.com>
> 
> If the kernel is locked down, require that all modules have valid
> signatures that we can verify.

Perhaps note that this won't cover the case where folk are using DM-Verity 
with a signed root hash for verifying kernel modules.


-- 
James Morris
<jmorris@...ei.org>