[
{
"acvVersion":"1.0"
},
{
"isSample":true,
"operation":"register",
"certificateRequest":"no",
"debugRequest":"yes",
"production":"no",
"encryptAtRest":"yes",
"algorithms":[
{
"revision":"2.0",
"algorithm":"ACVP-AES-XTS",
"prereqVals":[
{
"algorithm":"AES",
"valValue":"same"
},
{
"algorithm":"DRBG",
"valValue":"same"
}
],
"direction":[
"encrypt",
"decrypt"
],
"keyLen":[
128,
256
],
"payloadLen":[
{
"min":128,
"max":65536,
"increment":128
}
],
"tweakMode":[
"hex"
],
"dataUnitLen":[
{
"min":1024,
"max":65536,
"increment":128
}
],
"dataUnitLenMatchesPayload":false
},
...
]
}
]
Process the vectors and obtain the same results as the expected answers.
Vectors results differ from the expected answers when dataUnitLen differs from payloadLen .
We kindly ask to confirm the ACVP server logic behind the tweak value increment when dataUnitLen can differ from payloadLen.
We provide below an example:
environment
Demo
testSessionId
464670
vsId
2025897
Algorithm registration
Expected behavior
Process the vectors and obtain the same results as the expected answers.
Actual behavior
Vectors results differ from the expected answers when dataUnitLen differs from payloadLen .
We kindly ask to confirm the ACVP server logic behind the tweak value increment when dataUnitLen can differ from payloadLen.
We provide below an example:
It seems there's a similar issue #1475