From: "Stephan Müller" <smueller@chronox.de>
To: linux-crypto@vger.kernel.org
Subject: Qualcomm QCE driver: XTS setkey only allows 128 bit AES
Date: Mon, 13 Feb 2017 16:30:04 +0100 [thread overview]
Message-ID: <1690729.u0Mf5VzSsv@tauon.atsec.com> (raw)
Hi,
The Qualcomm QCE driver implementation defines:
.flags = QCE_ALG_AES | QCE_MODE_XTS,
.name = "xts(aes)",
.drv_name = "xts-aes-qce",
.blocksize = AES_BLOCK_SIZE,
.ivsize = AES_BLOCK_SIZE,
.min_keysize = AES_MIN_KEY_SIZE,
.max_keysize = AES_MAX_KEY_SIZE,
and
alg->cra_ablkcipher.min_keysize = def->min_keysize;
alg->cra_ablkcipher.max_keysize = def->max_keysize;
alg->cra_ablkcipher.setkey = qce_ablkcipher_setkey;
Thus, this driver has the limits of 128 to 256 bits for the key. Furthermore,
the common setkey function is used.
May I ask how the key for AES XTS is supposed to be handled here considering
that the kernel crypto API expects that the AES key and the tweak key is set
via one setkey call. I.e. the setkey should expect 256 through 512 bits.
Thanks.
Ciao
Stephan
next reply other threads:[~2017-02-13 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 15:30 Stephan Müller [this message]
2017-02-15 4:02 ` Qualcomm QCE driver: XTS setkey only allows 128 bit AES Herbert Xu
2017-02-15 7:28 ` Stephan Müller
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=1690729.u0Mf5VzSsv@tauon.atsec.com \
--to=smueller@chronox.de \
--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