5 Commits

Author	SHA1	Message	Date
Jaeden Amero	c28012acdd	tests: Remove NIST AES-XTS test vectors ... The IEEE P1619 XTS test vectors should suffice. Remove the NIST test vectors.	2018-06-13 12:13:58 +01:00
Jaeden Amero	142383e25b	aes: xts: Add tests for invalid key sizes ... Test that we get the error we expect when using various valid and invalid keysizes with mbedtls_aes_xts_setkey_enc() and mbedtls_aes_xts_setkey_dec().	2018-06-13 12:13:58 +01:00
Jaeden Amero	425382d4fb	tests: Extend AES-XTS suite ... Extend the existing test suite for AES-XTS with checks for error reporting and the IEEE P1619/D16 test vectors.	2018-06-13 12:05:04 +01:00
Jaeden Amero	e5c4b07b92	tests: Make AES-XTS suite more stack friendly ... Remove stack-allocated buffers from the AES-XTS test suites.	2018-06-13 12:05:04 +01:00
Aorimn	5f77801ac3	Implement AES-XTS mode ... XTS mode is fully known as "xor-encrypt-xor with ciphertext-stealing". This is the generalization of the XEX mode. This implementation is limited to an 8-bits (1 byte) boundary, which doesn't seem to be what was thought considering some test vectors [1]. This commit comes with tests, extracted from [1], and benchmarks. Although, benchmarks aren't really nice here, as they work with a buffer of a multiple of 16 bytes, which isn't a challenge for XTS compared to XEX. [1] http://csrc.nist.gov/groups/STM/cavp/documents/aes/XTSTestVectors.zip	2018-06-13 12:03:27 +01:00