KMAC MVT tests ignoring customization string, likely issue in AFT as well #904
Description
environment
demo
testSessionId
92033
vsId
241703
Algorithm registration
[{"acvVersion":"1.0"},{"isSample":true,"algorithms":[{"algorithm":"KMAC-128","revision":"1.0","hexCustomization":false,"xof":[true,false],"msgLen":[{"min":0,"max":1024,"increment":8}],"keyLen":[{"min":128,"max":1024,"increment":8}],"macLen":[{"min":32,"max":512,"increment":8}]},{"algorithm":"KMAC-256","revision":"1.0","hexCustomization":false,"xof":[true,false],"msgLen":[{"min":0,"max":65536,"increment":8}],"keyLen":[{"min":128,"max":4096,"increment":8}],"macLen":[{"min":32,"max":4096,"increment":8}]}]}]
Endpoint in which the error is experienced
https://demo.acvts.nist.gov:443/acvp/v1 GET
Expected behavior
The attached files have the validation tests hard-coded to ignore the customization string but they all pass as indicated by what's in the .res.json file. They shouldn't.
Additional context
There seems to be a general problem in the xof-cSHAKE tests with the customizationHex/customization test fields. I've also had a failure in another one of these by setting hexCustomization to true. Not sure if it's also related to the value being ignored, but it might be.
There is something clearly wrong with the processing of the AFT vectors as well. I'm not sure what it is though, but as I'm producing the same results as the server for validation if I ignore the customization string, I think the fundamental KMAC implementation is correct, but that something is going wrong with the passing in of the test data. If it is any help the attached AFT responses do use the customization string, I only disabled it for the MVT tests.