From: Joel Fernandes <joelf@ti.com>
To: <jussi.kivilinna@mbnet.fi>
Cc: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: [RFC] Unaligned CTR mode tests in crypto/testmgr.h
Date: Tue, 29 Oct 2013 19:11:23 -0500 [thread overview]
Message-ID: <52704EAB.5000308@ti.com> (raw)
Hi,
Some tests such as test 5 in AES CTR mode in crypto/testmgr.h have a unaligned
input buffer size such as 499 which is not aligned to any > 0 power of 2.
Due to this, omap-aes driver, and I think atmel-aes too error out when
encryption is requested for these buffers.
pr_err("request size is not exact amount of AES blocks\n") or a similar message.
Is this failure considered a bug? How do we fix it?
How were the result output vectors generated, did you use 0 padding? Do we 0 pad
the inputs to align in these cases to get correct results?
thanks,
-Joel
next reply other threads:[~2013-10-30 0:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 0:11 Joel Fernandes [this message]
2013-10-30 1:54 ` [RFC] Unaligned CTR mode tests in crypto/testmgr.h Herbert Xu
2013-10-30 18:34 ` Fernandes, Joel
2013-10-30 11:09 ` Jussi Kivilinna
2013-10-30 21:06 ` Joel Fernandes
2013-10-31 8:40 ` Jussi Kivilinna
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=52704EAB.5000308@ti.com \
--to=joelf@ti.com \
--cc=jussi.kivilinna@mbnet.fi \
--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 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).