-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for "alternate" SHA Monte Carlo Tests on demo server? #289
Comments
Hi @ott-kiwi, can you provide me a VS/Test ID for the failure? |
"vsId": 1833519 The lab ran my results and I got all passes for the AFTs, but the (alternate) MCT results just gave: If I had the iterations for the inner loop I might be able to track down the problem (if it's our end).... |
Appreciated, I'll look into for you. |
Thanks jbrock24. I'm pretty sure it's something to do with the padding. SHA-1 and SHA256 both require padding with zeros after the first few iterations whereas SHA384 and SHA512 do not. If it helps, here my debug for the first 8 iterations of the first run through the inner loop: [ACVP]: Found new hash test vector... |
Appreciated |
It looks to me like there is a problem at line 75 in AlternateSizeShaMct.cs where:
should be
When I remove the zero padding from the data to be hashed, I get a match with the expected. |
@ott-kiwi Was definitely an issue, fixed that and am currently testing. Appreciate the feedback a lot, it will go out with the next update and we'll let you know when it's published. Thanks again! |
The fix for this is on Demo in release v1.1.0.32. |
The fix for this is on Prod in release v1.1.0.32. |
I have sample vectors and expected results from a lab for the Monte Carlo "alternate" tests which, when run for SHA384 and SHA512 work fine. When running exactly the same tests with the only change being the md method (SHA-1 or SHA256), the AFT tests match the expected but not the MCT tests. I've broken it down to smaller pieces and verified using online sha calculators that the hashes are correct, but am otherwise at a complete loss why I'm not getting the expected result after 1000 iterations. I'd like to verify that it works using samples from the demo server, but currently it seems the demo only provides "standard" MCT tests. Are there any plans to support "alternate" MCT's in the demo environment any time soon? If not, any pointers as to what might be going wrong?
The text was updated successfully, but these errors were encountered: