search

usnistgov / ACVP-Server

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

AES-CTR Vectors Not Matching Expected Results #192

Closed Kneckter closed 2 years ago

Kneckter commented 2 years ago

Since the v1.1.0.24 update on the Demo server, the AES-CTR expected results have not been matching actual results. Most values are off by 1 bit e.g., expected result is "604710144BD724AC8DF90972C3F8E5B9" and recorded result is "604710144BD724AC8DF90972C3F8E5B8”. I've tested this about 5 times with new demo sets and different crypto libraries but the results do not match and have the single bit shift.

I ran a vector set from Jan 15th and the results were match to the expected results.

Is anyone else experiencing this mismatch?

For reference: 905837_ACVP-AES-CTR-Tests.txt 905837_ACVP-AES-CTR-Expected.txt 905837_ACVP-AES-CTR-Recorded.txt

livebe01 commented 2 years ago

Hi @Kneckter, have you had any luck resolving this issue? I looked back through the last week's worth of traffic on demo and we haven't had any AES-CTR vector sets fail for that time period.

Kneckter commented 2 years ago

Thanks for replying. I think I have it figured out but had to work on something else. I'm going to close this issue in the meantime.