crypto: talitos: Add AES-XTS mode
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 18 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | crypto: talitos: Clean ups and comment fixes for ablkcipher commandsdrivers/ | +4 | 0 replies | |
| 2/2 | crypto: talitos: Add AES-XTS Supportdrivers/ drivers/ | +34 | 6 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] crypto: talitos: Add AES-XTS mode
This adds the AES-XTS mode, supported by the Freescale SEC 3.3.2.
One of the nice things about this hardware is that it knows how to deal with encrypt/decrypt requests that are larger than sector size, but that also requires that that the sector size be passed into the crypto engine as an XTS cipher context parameter.
When a request is larger than the sector size the sector number is incremented by the talitos engine and the tweak key is re-calculated for the new sector.
I've tested this with 256bit and 512bit keys (tweak and data keys of 128bit and 256bit) to ensure interoperability with the software AES-XTS implementation. All testing was done using dm-crypt/LUKS with aes-xts-plain64.
Is there a better solution that just hard coding the sector size to (1<<SECTOR_SHIFT)? Maybe dm-crypt should be modified to pass the sector size along with the plain/plain64 IV to an XTS algorithm?
Martin Hicks (2):
crypto: talitos: Clean ups and comment fixes for ablkcipher commands
crypto: talitos: Add AES-XTS Support
drivers/crypto/talitos.c | 45 +++++++++++++++++++++++++++++++++++++-------- drivers/crypto/talitos.h | 1 + 2 files changed, 38 insertions(+), 8 deletions(-)
Signature · 1 line
1.7.10.4