All of lore.kernel.org
 help / color / mirror / Atom feed
From: leroy christophe <christophe.leroy@c-s.fr>
To: Kim Phillips <kim.phillips@freescale.com>
Cc: linux-crypto@vger.kernel.org
Subject: Re: Parity Error on keys used for DES crypto test
Date: Thu, 24 Apr 2014 15:08:57 +0200	[thread overview]
Message-ID: <53590CE9.7030607@c-s.fr> (raw)
In-Reply-To: <20140423185813.c885f8de953ed216b8895437@freescale.com>


Le 24/04/2014 01:58, Kim Phillips a écrit :
> On Wed, 23 Apr 2014 10:20:16 +0200
> leroy christophe <christophe.leroy@c-s.fr> wrote:
>
>> I'm altering the Freescale Talitos Driver in order to support the SEC1
>> security engine, and I have a big issue with the DES test vectors in
>> testmgr.h:
>>
>> The Sec Engine reports key parity error.
>>
>> Looking at the keys defined in testmgr.h for DES3, it looks like there
>> is a real parity issue with the test vectors. A DES key is supposed to
>> have all bytes with an odd number of ones. It is not the case in the key
>> below. At least the second byte 0xC0 has an even number of ones.
>>
>> static struct cipher_testvec des3_ede_cbc_enc_tv_template[] = {
>>       { /* Generated from openssl */
>>           .key    = "\xE9\xC0\xFF\x2E\x76\x0B\x64\x24"
>>                 "\x44\x4D\x99\x5A\x12\xD6\x40\xC0"
>>                 "\xEA\xC2\x84\xE8\x14\x95\xDB\xE8",
>>
>> So, how can this test vector work ?
> I'm not going to comment on the validity of the test key vector
> other than to say that you can turn off key parity errors in the
> SEC1 in the DEU Interrupt Control Register.
>
> Kim
>
Thanks, it works

Christophe

      reply	other threads:[~2014-04-24 13:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-23  8:20 Parity Error on keys used for DES crypto test leroy christophe
2014-04-23 23:58 ` Kim Phillips
2014-04-24 13:08   ` leroy christophe [this message]

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=53590CE9.7030607@c-s.fr \
    --to=christophe.leroy@c-s.fr \
    --cc=kim.phillips@freescale.com \
    --cc=linux-crypto@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.