linux-kernel - Re: sign-file and detached PKCS#7 firmware signatures

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: <7182.1432067349@warthog.procyon.org.uk>
Date:	Tue, 19 May 2015 21:29:09 +0100
From:	David Howells <dhowells@...hat.com>
To:	"Luis R. Rodriguez" <mcgrof@...e.com>
Cc:	dhowells@...hat.com, Rusty Russell <rusty@...tcorp.com.au>,
	Michal Marek <mmarek@...e.cz>,
	Matthew Garrett <mjg59@...f.ucam.org>, keyrings@...ux-nfs.org,
	dmitry.kasatkin@...il.com,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Seth Forshee <seth.forshee@...onical.com>,
	linux-security-module <linux-security-module@...r.kernel.org>,
	David Woodhouse <dwmw2@...radead.org>
Subject: Re: sign-file and detached PKCS#7 firmware signatures

Luis R. Rodriguez <mcgrof@...e.com> wrote:

> > Though you would still have to be careful with firmware loaded during the
> > initramfs phase.
> 
> Make sense, how about:
> 
> ---
> The $DIGEST_ALGORITHM needs to be enabled as built-in (=y) or modular
> (=m) in the running kernel and can differ from CONFIG_MODULE_SIG_HASH.
> If you are enabling the $DIGEST_ALGORITHM as a module take care to
> ensure that this module will also be present on the initramfs used as
> some modules within the initramfs may need it if using the

Some firmware signatures, not modules.

> firmware_class APIs and firmware signing has been enabled.
> ---

David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/