linux-kernel - Transferring applied X.509 patches from crypto/next to security/next

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:	Mon, 08 Feb 2016 13:58:34 +0000
From:	David Howells <dhowells@...hat.com>
To:	Herbert Xu <herbert@...dor.apana.org.au>
Cc:	dhowells@...hat.com, jmorris@...ei.org,
	Tadeusz Struk <tadeusz.struk@...el.com>,
	linux-kernel@...r.kernel.org,
	linux-security-module@...r.kernel.org,
	linux-crypto@...r.kernel.org, zohar@...ux.vnet.ibm.com
Subject: Transferring applied X.509 patches from crypto/next to security/next

Herbert Xu <herbert@...dor.apana.org.au> wrote:

> > Hmmm...  That means that the crypto branch and the security branch are going
> > to conflict.
> 
> I thought you were OK with it going in now as you said that you'll
> fix it up later.  Sorry for the misunderstanding.  Do you want me to
> revert?

If you can back them out, I'll apply them to my keys-next branch.  Unless
James is willing to rebase security/next on top of your crypto branch?

David