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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 10 Jul 2014 17:47:28 +0300
From:	Dmitry Kasatkin <>
To:	Mimi Zohar <>,
	David Howells <>
Cc:	keyrings <>,
	linux-security-module <>,
	linux-kernel <>,
	Josh Boyer <>,
	Matthew Garrett <>,
	Dmitry Kasatkin <>
Subject: Re: [PATCH v6 0/6] ima: extending secure boot certificate chain of

Hi David,

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 would do it with different pull requests.

- Dmitry

On 10/07/14 00:29, Mimi Zohar wrote:
> On Wed, 2014-07-09 at 19:56 +0100, David Howells wrote: 
>> Mimi Zohar <> wrote:
>>> 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.
>> There is overlap in the X.509 certificate request function that you took from
>> my pkcs#7 patches.
> Right, x509_request_asymmetric_key() is the same as
> pkcs7_request_asymmetric_key().
> Mimi
> --
> To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
> the body of a message to
> More majordomo info at

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists