From: "Longpeng (Mike)" <longpeng2@huawei.com>
To: Jussi Kivilinna <jussi.kivilinna@iki.fi>
Cc: <jussi.kivilinna@haltian.com>, <herbert@gondor.apana.org.au>,
Gonglei <arei.gonglei@huawei.com>,
"Zhoujian (jay, Euler)" <jianjay.zhou@huawei.com>,
"Wubin (H)" <wu.wubin@huawei.com>, <linux-kernel@vger.kernel.org>
Subject: Re: Question about ctr mode 3des-ede IV len
Date: Thu, 8 Dec 2016 19:29:54 +0800 [thread overview]
Message-ID: <58494432.3010102@huawei.com> (raw)
In-Reply-To: <493854a6-4e80-849a-cffb-e2f5a29a009e@iki.fi>
Hi Jussi,
On 2016/12/7 21:15, Jussi Kivilinna wrote:
> Hello,
>
> 07.12.2016, 14:43, Longpeng (Mike) kirjoitti:
>> Hi Jussi and Herbert,
>>
>> I saw serveral des3-ede testcases(in crypto/testmgr.h) has 16-bytes IV, and the
>> libgcrypt/nettle/RFC1851 said the IV-len is 8-bytes.
>>
>> Would you please tell me why these testcases has 16-bytes IV ?
>
> Because I used same tool to create test-vectors which I had previously used to create AES/Camellia/Serpent/Twofish test-vectors. So, I must have forgotten to change 16-byte IV generation to 8 bytes and thus those testcases in crypto/testmgr.h have wrong length. The extra trailing 8 bytes are not used and can be removed.
>
Thank you very much. :)
> -Jussi
>
>>
>> Thank you. :)
>>
>
> .
>
--
Regards,
Longpeng(Mike)
next prev parent reply other threads:[~2016-12-08 11:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 12:43 Question about ctr mode 3des-ede IV len Longpeng (Mike)
2016-12-07 13:15 ` Jussi Kivilinna
2016-12-08 11:29 ` Longpeng (Mike) [this message]
2016-12-08 9:04 ` Herbert Xu
2016-12-08 9:12 ` Longpeng (Mike)
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=58494432.3010102@huawei.com \
--to=longpeng2@huawei.com \
--cc=arei.gonglei@huawei.com \
--cc=herbert@gondor.apana.org.au \
--cc=jianjay.zhou@huawei.com \
--cc=jussi.kivilinna@haltian.com \
--cc=jussi.kivilinna@iki.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=wu.wubin@huawei.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 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.