From: Kirill Marinushkin <k.marinushkin@gmail.com>
To: dhowells@redhat.com
Cc: asavkov@redhat.com, k.marinushkin@gmail.com,
paul.gortmaker@windriver.com, james.l.morris@oracle.com,
keyrings@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] security/keys: make BIG_KEYS dependent on stdrng.
Date: Tue, 6 Sep 2016 18:32:27 +0200 [thread overview]
Message-ID: <1473179547-12101-1-git-send-email-k.marinushkin@gmail.com> (raw)
In-Reply-To: <32083.1473167516@warthog.procyon.org.uk>
> The other thing is that I have been given a conflicting patch (see
> below). Is your fix preferable?
The patch you attached previously is v1; I submitted v2 after review by
Stephan Mueller. I additionally attach it here below.
IMO, the preferable fix depends on your future plan.
If you plan to continue using both ANSI X9.31 DRNG and DRBG - I agree with the
patch suggested by Artem Savkov.
If you plan to reduce using ANSI X9.31 DRNG and use DRBG more widely - I
suggest my patch.
Best Regards,
Kirill
---
From Kirill Marinushkin <k.marinushkin@gmail.com>
Subject [PATCH v2] KEYS: fix big_key dependency
Date Tue, 16 Aug 2016 21:51:12 +0200
This patch fixes the following bug:
[oss-security] - panic at big_key_preparse #4.7-r6/rc7 & master
Signed-off-by: Kirill Marinushkin <k.marinushkin@gmail.com>
---
security/keys/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/security/keys/Kconfig b/security/keys/Kconfig
index f826e87..5bc5114 100644
--- a/security/keys/Kconfig
+++ b/security/keys/Kconfig
@@ -44,7 +44,7 @@ config BIG_KEYS
select CRYPTO
select CRYPTO_AES
select CRYPTO_ECB
- select CRYPTO_RNG
+ select CRYPTO_RNG_DEFAULT
next prev parent reply other threads:[~2016-09-06 16:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-05 12:37 [PATCH] security/keys: make BIG_KEYS dependent on stdrng Artem Savkov
2016-09-06 12:58 ` David Howells
2016-09-06 13:06 ` Artem Savkov
2016-09-06 13:11 ` David Howells
2016-09-06 13:16 ` Stephan Mueller
2016-09-06 13:25 ` Artem Savkov
2016-09-06 16:32 ` Kirill Marinushkin [this message]
2016-09-06 18:16 ` David Howells
2016-10-06 8:00 ` Artem Savkov
2016-10-24 14:50 ` David Howells
2016-10-25 10:26 ` Artem Savkov
2016-10-25 11:37 ` David Howells
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1473179547-12101-1-git-send-email-k.marinushkin@gmail.com \
--to=k.marinushkin@gmail.com \
--cc=asavkov@redhat.com \
--cc=dhowells@redhat.com \
--cc=james.l.morris@oracle.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).