On Thu, Jul 17, 2014 at 10:55 PM, David Howells <dhowells@xxxxxxxxxx> wrote: > Dmitry Kasatkin <d.kasatkin@xxxxxxxxxxx> 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. > Oops, this is not what I wanted to have. Yes, I wanted to have still them under crypto but wanted to break dependency. I was hurrying before starting the holidays, tested only from command line, but did not look to menuconfig. In overall asymmetric keys does not provide any crypto API. Instead they provide key types... They use crypto api them in couple of places. So it is more about "selecting" crypto. In my opinion "entire" location of asymmetric keys under /crypto is wrong. RSA algo may be there, but reset of the stuff can be under /keys. -Dmitry > 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-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
