From: "Leonidas S. Barbosa" <leosilva@linux.vnet.ibm.com>
To: linux-crypto@vger.kernel.org
Cc: mhcerri@linux.vnet.ibm.com
Subject: tcrypt rfc4309 ccm test keys size issue
Date: Thu, 18 Sep 2014 15:43:02 -0300 [thread overview]
Message-ID: <20140918184302.GA19143@bluepex.com> (raw)
Hi,
I'm facing an issue running tcrypt with rfc4309-aes-ccm.
My hardware and drive only implements support to key size 128, what is
specify in the documentation (http://tools.ietf.org/html/rfc4309) as a
'MUST' support, but does not support the other sizes. However tcrypt
tests
not only 128, but also 192 and 256bits size, which in ietf documentation
are 'MAY' also support.
The issue is if I run my machines with FIPS enable it won't work
at all, since tcrypt will try to the other key sizes and so fails making
my system crash in a kernel panic.
I wondering if this tcrypt to 192 and 256 are correct since it's not
a 'MUST' support size. Either if have any option to disable tcrypt to
test with this other key sizes. And once more, since they are not a must
support, what is the history about this test?
A workround for us in the moment is to disable ccm in FIPs mode.
Best regards,
Leonidas.)
reply other threads:[~2014-09-18 18:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140918184302.GA19143@bluepex.com \
--to=leosilva@linux.vnet.ibm.com \
--cc=linux-crypto@vger.kernel.org \
--cc=mhcerri@linux.vnet.ibm.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.