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: <1405516544.1466.50.camel@dhcp-9-2-203-236.watson.ibm.com>
Date:	Wed, 16 Jul 2014 09:15:44 -0400
From:	Mimi Zohar <zohar@...ux.vnet.ibm.com>
To:	David Howells <dhowells@...hat.com>
Cc:	Dmitry Kasatkin <d.kasatkin@...sung.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

On Sun, 2014-07-13 at 22:06 +0100, David Howells wrote: 
> 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.

We're already at -rc5.  Any pull requests for the next open window need
to submitted soon.  If/when are you planning on sending James the pull
request?  (I'm kind of waiting for the KEY patches to make it in, before
sending the linux-integrity pull request.)

thanks,

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ