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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 17 Jul 2014 20:55:53 +0100 From: David Howells <dhowells@...hat.com> To: Dmitry Kasatkin <d.kasatkin@...sung.com> Cc: dhowells@...hat.com, zohar@...ux.vnet.ibm.com, linux-security-module@...r.kernel.org, linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org, dmitry.kasatkin@...il.com Subject: Making the asymmetric keys config option into a top-level option Dmitry Kasatkin <d.kasatkin@...sung.com> wrote: > When ASYMMETRIC_KEYS=y, but depends on CRYPTO=m, selections will be also modules. > In random config case OID_REGISTRY, MPILIB and ASN1 became modules producing build > break. This patch removes asymmetric keys dependency from CRYPTO, but instead > selects CRYPTO and CRYPTO_HASH as they are needed. You do realise that this makes the asymmetric key config option into a top-level option? I think, logically, that's the wrong thing to do. They should still appear under the crypto menu. Note that I think your patch is really the wrong solution. The right solution is to fix the configuration tools - but that's quite an undertaking. David -- 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