linux-kernel - Re: [PATCH v6 0/6] ima: extending secure boot certificate chain of trust

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:	Sun, 13 Jul 2014 22:06:59 +0100
From:	David Howells <dhowells@...hat.com>
To:	Dmitry Kasatkin <d.kasatkin@...sung.com>
Cc:	dhowells@...hat.com, Mimi Zohar <zohar@...ux.vnet.ibm.com>,
	keyrings <keyrings@...ux-nfs.org>,
	linux-security-module <linux-security-module@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Josh Boyer <jwboyer@...hat.com>,
	Matthew Garrett <mjg59@...f.ucam.org>,
	Dmitry Kasatkin <dmitry.kasatkin@...il.com>
Subject: Re: [PATCH v6 0/6] ima: extending secure boot certificate chain of trust

Dmitry Kasatkin <d.kasatkin@...sung.com> wrote:

> If patches from integrity/next-trusted-keys goes via your tree, then I
> suggest that you re-base your patches on the top of our
> patchset, because it is unclear how long review of PE, PKCS7 patches
> will take and if they will be pulled...

I'd rather not do that since other things are now depending on my patches.

What's probably better is just to clean up the duplication later.  That way,
there need be no dependency between the two sets.

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/