linux-kernel - Moving asymmetric keys from crypto/ to security/keys/

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>] [day] [month] [year] [list]

Message-ID: <776.1460551538@warthog.procyon.org.uk>
Date:	Wed, 13 Apr 2016 13:45:38 +0100
From:	David Howells <dhowells@...hat.com>
To:	jmorris@...ei.org, herbert@...dor.apana.org.au
cc:	dhowells@...hat.com, keyrings@...r.kernel.org,
	linux-crypto@...r.kernel.org,
	linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Moving asymmetric keys from crypto/ to security/keys/

Hi James, Herbert,

Since the actual crypto bits (RSA) have been extracted from the asymmetric
keys code and moved to base crypto, shall I move the asymmetric_keys/ subdir
over to security/keys/?

If so, how best to do it?  I'm thinking that it might be best for me to create
a git branch that effects the change and then have both of you merge it so
that when Linus pulls your stuff in the next merge window git just handles it.

That said, there is a change to the PKCS#7 code in Herbert's tree that's not
in security/next or upstream which complicates matters - though possibly this
being fixed up in the merge will be handled by git.

David