From: Jarod Wilson <jarod@redhat.com>
To: linux-crypto@vger.kernel.org
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
Neil Horman <nhorman@tuxdriver.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] crypto: des3_ede: permit weak keys unless REQ_WEAK_KEY set
Date: Fri, 05 Dec 2008 10:03:53 -0500 [thread overview]
Message-ID: <493942D9.6030807@redhat.com> (raw)
In-Reply-To: <200812041557.49601.jarod@redhat.com>
Jarod Wilson wrote:
> While its a slightly insane to bypass the key1 == key2 ||
> key2 == key3 check in triple-des, since it reduces it to the
> same strength as des, some folks do need to do this from time
> to time for backwards compatibility with des.
>
> My own case is FIPS CAVS test vectors. Many triple-des test
> vectors use a single key, replicated 3x. In order to get the
> expected results, des3_ede_setkey() needs to honor the weak
> key flag.
>
> Also adds a warning when a weak key is rejected, otherwise,
> you silently get back a bogus result.
>
> Signed-off-by: Jarod Wilson <jarod@redhat.com>
v2: make CRYPTO_TFM_REQ_WEAK_KEY flag usage consistent w/rest of crypto
subsystem, per comments from Herbert in Red Hat bugzilla #474394.
---
crypto/des_generic.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/crypto/des_generic.c b/crypto/des_generic.c
index 5d0e458..9002073 100644
--- a/crypto/des_generic.c
+++ b/crypto/des_generic.c
@@ -868,7 +868,8 @@ static int des3_ede_setkey(struct crypto_tfm *tfm,
const u8 *key,
u32 *flags = &tfm->crt_flags;
if (unlikely(!((K[0] ^ K[2]) | (K[1] ^ K[3])) ||
- !((K[2] ^ K[4]) | (K[3] ^ K[5]))))
+ !((K[2] ^ K[4]) | (K[3] ^ K[5]))) &&
+ (*flags & CRYPTO_TFM_REQ_WEAK_KEY))
{
*flags |= CRYPTO_TFM_RES_BAD_KEY_SCHED;
return -EINVAL;
--
Jarod Wilson
jarod@redhat.com
next parent reply other threads:[~2008-12-05 15:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200812041557.49601.jarod@redhat.com>
2008-12-05 15:03 ` Jarod Wilson [this message]
2008-12-05 15:24 ` [PATCH v2] crypto: des3_ede: permit weak keys unless REQ_WEAK_KEY set Herbert Xu
2008-12-06 5:39 ` [PATCH v3] " Jarod Wilson
2008-12-06 20:17 ` Neil Horman
2008-12-07 11:38 ` Herbert Xu
[not found] ` <200812051458.10426.jarod@redhat.com>
2008-12-08 15:41 ` [PATCH v4] " Jarod Wilson
2008-12-17 5:51 ` Herbert Xu
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=493942D9.6030807@redhat.com \
--to=jarod@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nhorman@tuxdriver.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