Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1317011 > unrolled thread
| Started by | Arnd Bergmann <arnd@arndb.de> |
|---|---|
| First post | 2016-01-25 18:00 +0100 |
| Last post | 2016-01-26 13:00 +0100 |
| Articles | 3 — 2 participants |
Back to article view | Back to linux.kernel
[PATCH 1/2] crypto: jitterentropy - always select CRYPTO_RNG Arnd Bergmann <arnd@arndb.de> - 2016-01-25 18:00 +0100
Re: [PATCH 1/2] crypto: jitterentropy - always select CRYPTO_RNG Herbert Xu <herbert@gondor.apana.org.au> - 2016-01-26 11:40 +0100
Re: [PATCH 1/2] crypto: jitterentropy - always select CRYPTO_RNG Arnd Bergmann <arnd@arndb.de> - 2016-01-26 13:00 +0100
| From | Arnd Bergmann <arnd@arndb.de> |
|---|---|
| Date | 2016-01-25 18:00 +0100 |
| Subject | [PATCH 1/2] crypto: jitterentropy - always select CRYPTO_RNG |
| Message-ID | <qUSEG-6QD-7@gated-at.bofh.it> |
When building the jitterentropy driver by itself, we get a link error when CRYPTO_RNG is not enabled as well: crypto/built-in.o: In function `jent_mod_init': jitterentropy-kcapi.c:(.init.text+0x98): undefined reference to `crypto_register_rng' crypto/built-in.o: In function `jent_mod_exit': jitterentropy-kcapi.c:(.exit.text+0x60): undefined reference to `crypto_unregister_rng' This moves the 'select CRYPTO_RNG' from CRYPTO_DRBG to CRYPTO_JITTERENTROPY to ensure the API is always there when it's used, not just when DRBG is also enabled. Signed-off-by: Arnd Bergmann <arnd@arndb.de> --- crypto/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/crypto/Kconfig b/crypto/Kconfig index 7240821137fd..99109b93604a 100644 --- a/crypto/Kconfig +++ b/crypto/Kconfig @@ -1586,13 +1586,13 @@ config CRYPTO_DRBG_CTR config CRYPTO_DRBG tristate default CRYPTO_DRBG_MENU - select CRYPTO_RNG select CRYPTO_JITTERENTROPY endif # if CRYPTO_DRBG_MENU config CRYPTO_JITTERENTROPY tristate "Jitterentropy Non-Deterministic Random Number Generator" + select CRYPTO_RNG help The Jitterentropy RNG is a noise that is intended to provide seed to another RNG. The RNG does not -- 2.7.0
[toc] | [next] | [standalone]
| From | Herbert Xu <herbert@gondor.apana.org.au> |
|---|---|
| Date | 2016-01-26 11:40 +0100 |
| Message-ID | <qV9cu-2Od-17@gated-at.bofh.it> |
| In reply to | #1317011 |
On Mon, Jan 25, 2016 at 05:50:34PM +0100, Arnd Bergmann wrote: > When building the jitterentropy driver by itself, we get a link error > when CRYPTO_RNG is not enabled as well: > > crypto/built-in.o: In function `jent_mod_init': > jitterentropy-kcapi.c:(.init.text+0x98): undefined reference to `crypto_register_rng' > crypto/built-in.o: In function `jent_mod_exit': > jitterentropy-kcapi.c:(.exit.text+0x60): undefined reference to `crypto_unregister_rng' > > This moves the 'select CRYPTO_RNG' from CRYPTO_DRBG to CRYPTO_JITTERENTROPY > to ensure the API is always there when it's used, not just when DRBG is > also enabled. > > Signed-off-by: Arnd Bergmann <arnd@arndb.de> > --- > crypto/Kconfig | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/crypto/Kconfig b/crypto/Kconfig > index 7240821137fd..99109b93604a 100644 > --- a/crypto/Kconfig > +++ b/crypto/Kconfig > @@ -1586,13 +1586,13 @@ config CRYPTO_DRBG_CTR > config CRYPTO_DRBG > tristate > default CRYPTO_DRBG_MENU > - select CRYPTO_RNG I think we should leave this there as DRBG itself is an RNG and it just uses JITTERENTROPY which happens to be an RNG. Otherwise this looks OK to me. Thanks, -- Email: Herbert Xu <herbert@gondor.apana.org.au> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
[toc] | [prev] | [next] | [standalone]
| From | Arnd Bergmann <arnd@arndb.de> |
|---|---|
| Date | 2016-01-26 13:00 +0100 |
| Message-ID | <qVarW-3A1-37@gated-at.bofh.it> |
| In reply to | #1317723 |
On Tuesday 26 January 2016 18:30:18 Herbert Xu wrote: > On Mon, Jan 25, 2016 at 05:50:34PM +0100, Arnd Bergmann wrote: > > When building the jitterentropy driver by itself, we get a link error > > when CRYPTO_RNG is not enabled as well: > > > > crypto/built-in.o: In function `jent_mod_init': > > jitterentropy-kcapi.c:(.init.text+0x98): undefined reference to `crypto_register_rng' > > crypto/built-in.o: In function `jent_mod_exit': > > jitterentropy-kcapi.c:(.exit.text+0x60): undefined reference to `crypto_unregister_rng' > > > > This moves the 'select CRYPTO_RNG' from CRYPTO_DRBG to CRYPTO_JITTERENTROPY > > to ensure the API is always there when it's used, not just when DRBG is > > also enabled. > > > > Signed-off-by: Arnd Bergmann <arnd@arndb.de> > > --- > > crypto/Kconfig | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff --git a/crypto/Kconfig b/crypto/Kconfig > > index 7240821137fd..99109b93604a 100644 > > --- a/crypto/Kconfig > > +++ b/crypto/Kconfig > > @@ -1586,13 +1586,13 @@ config CRYPTO_DRBG_CTR > > config CRYPTO_DRBG > > tristate > > default CRYPTO_DRBG_MENU > > - select CRYPTO_RNG > > I think we should leave this there as DRBG itself is an RNG and > it just uses JITTERENTROPY which happens to be an RNG. Good idea. Should I resend a modified version or do you want to just adapt it yourself? Arnd
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web