search

usnistgov / ACVP-Server

A repository tracking releases of NIST's ACVP server. See www.github.com/usnistgov/ACVP for the protocol.
46 stars 16 forks source link

Issue with AES KWP expected payloadLength #200

Closed afazio2 closed 1 year ago

afazio2 commented 2 years ago

environment Demo

testSessionId 240064

vsId 947110

Algorithm registration { "revision":"1.0", "algorithm":"ACVP-AES-KWP", "direction":[ "encrypt", "decrypt" ], "keyLen":[ 128, 192, 256 ], "payloadLen":[ 8, 72, 136, 240, 376, 568, 712, 808, 888, 1000 ], "ivLen":[ 64 ], "kwCipher":[ "cipher" ] }

Expected behavior Expect to receive Test Groups with different payloadLen values selected from [ 8, 72, 136, 240, 376, 568, 712, 808 , 888, 1000 ]

Received 6 test groups with the same payloadLen = 1000.

livebe01 commented 2 years ago

Thanks @afazio2. I've identified the issue on our end. We'll get a fix out for this in the next release. In the interim, using the payloadLen restrictions defined for AES-KW should get you better results.

afazio2 commented 2 years ago

Thank you for your support @livebe01. From AES-KW payloadLen restrictions, the increment is 64. If I needed to avoid multiples of 64 in my AES-KWP test vectors requests, could you please describe how to do it ?

livebe01 commented 2 years ago

If you need to avoid multiples of 64 in your testing, you will need to wait until we get a fix out in our next release.

livebe01 commented 2 years ago

The fix for this is now on Demo, v1.1.0.25.

livebe01 commented 1 year ago

The fix for this is now on Prod in release v1.1.0.25.