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]

Message-ID: <1404924054.14643.36.camel@dhcp-9-2-203-236.watson.ibm.com>
Date:	Wed, 09 Jul 2014 12:40:54 -0400
From:	Mimi Zohar <zohar@...ux.vnet.ibm.com>
To:	David Howells <dhowells@...hat.com>
Cc:	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

On Wed, 2014-07-09 at 16:31 +0100, David Howells wrote: 
> Okay, I've merged a number of patchsets together that I want to push for the
> next merge window:
> 
> 	http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=keys-next
> 
> I'd like to add yours.  Shall I pull:
> 
> 	linux-integrity/next-trusted-keys
> 
> which is here, I presume:
> 
> 	http://git.kernel.org/cgit/linux/kernel/git/zohar/linux-integrity.git/
> 

Yes, that's fine.  My concern, however, is that the trusted keyring
patches are independent of the other patches being upstreamed and should
be upstreamed regardless of the other patches.

Mimi

--
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/