From: Anatoly Pugachev <matorola@xxxxxxxxx> Date: Wed, 4 May 2016 22:10:47 +0300 > Here's a quick diff related to crypto for debian kernel configs: > > $ diff -u /boot/config-4.5.0-2-sparc64-smp /boot/config-4.6.0-rc5-sparc64-smp > @@ -5299,10 +5380,9 @@ > CONFIG_CRYPTO_RNG=m > CONFIG_CRYPTO_RNG2=y > CONFIG_CRYPTO_RNG_DEFAULT=m > -CONFIG_CRYPTO_PCOMP=m > -CONFIG_CRYPTO_PCOMP2=y > CONFIG_CRYPTO_AKCIPHER2=y > -# CONFIG_CRYPTO_RSA is not set > +CONFIG_CRYPTO_AKCIPHER=y > +CONFIG_CRYPTO_RSA=y > CONFIG_CRYPTO_MANAGER=y > CONFIG_CRYPTO_MANAGER2=y > # CONFIG_CRYPTO_USER is not set > > so, I need to compile 4.5.x kernel (or even older kernels) with > CRYPTO_RSA=y and test how it would act. Well yes, that would be an absolutely critical datapoint. -- 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
