Am Montag, 23. April 2018, 07:51:35 CEST schrieb Jitendra Lulla: Hi Jitendra,
> > TEST 2: > > Similarly for XTS also we have one mismatch: > https://csrc.nist.gov/CSRC/media/Projects/Cryptographic-Algorithm-Validation > -Program/documents/aes/XTSTestVectors.zip > > /XTSTestVectors/format tweak value input - 128 hex str/XTSGenAES256.rsp > > kcapi -x 1 -e -c "xts(aes)" -k > 31c8152b5eddc3b8c3a005a3bbc4c005bb57058ae4a6454c166a620389eaecaea0515433574b > 0dd6a89496acd475ef78dcf012a47a48c319f89e931404018e15 -p > 31761b6dece3e962030c01f481c5ca681386176d2ef8034c5db5aa04b613ec00 -i > 6957d297dc9c9b30f6d016b016d913c5 > > Result from tool : > 1e16b5a44274f8791508cf3dec971aa975e16c702d66f11bc1f00ede540ef82c > > NIST Expected Result : > ae13222810bc66997bf8b57737990e481e16b5a44274f8791508cf3dec971a80 The mentioned test vector is decryption and not encryption as you applied it. Then, the data unit length in the test vector is 250 and not a multiple of 128 which is the one to be used for XTS here. Bottom line, the test vector is not applicable. Ciao Stephan
