From: Neil Horman <nhorman@tuxdriver.com>
To: Jarod Wilson <jarod@redhat.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] crypto: des3_ede: permit weak keys unless REQ_WEAK_KEY set
Date: Sat, 6 Dec 2008 15:17:20 -0500 [thread overview]
Message-ID: <20081206201720.GA18783@localhost.localdomain> (raw)
In-Reply-To: <493A101A.1080500@redhat.com>
On Sat, Dec 06, 2008 at 12:39:38AM -0500, Jarod Wilson wrote:
> 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.
>
> v2: make CRYPTO_TFM_REQ_WEAK_KEY flag usage consistent w/rest
> of crypto subsystem, per comments from Herbert in Red Hat
> bugzilla #474394.
>
> v3: set more appropriate RES flag, also per Herbert.
>
> Signed-off-by: Jarod Wilson <jarod@redhat.com>
>
> ---
> crypto/des_generic.c | 5 +++--
> 1 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/crypto/des_generic.c b/crypto/des_generic.c
> index 5d0e458..5bd3ee3 100644
> --- a/crypto/des_generic.c
> +++ b/crypto/des_generic.c
> @@ -868,9 +868,10 @@ 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;
> + *flags |= CRYPTO_TFM_RES_WEAK_KEY;
> return -EINVAL;
> }
>
>
Looks good to me. Thanks Jarod!
Acked-by: Neil Horman <nhorman@tuxdriver.com>
next prev parent reply other threads:[~2008-12-06 20:19 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 ` [PATCH v2] crypto: des3_ede: permit weak keys unless REQ_WEAK_KEY set Jarod Wilson
2008-12-05 15:24 ` Herbert Xu
2008-12-06 5:39 ` [PATCH v3] " Jarod Wilson
2008-12-06 20:17 ` Neil Horman [this message]
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=20081206201720.GA18783@localhost.localdomain \
--to=nhorman@tuxdriver.com \
--cc=herbert@gondor.apana.org.au \
--cc=jarod@redhat.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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