Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes the testvector mismatch introduced in #244.
A bit more history.
In the PR #128, there was the same issue. But this was identified and fixed before merging to pqm4. The problem is that the element 3329 should be mapped to 0 while packing to the public key array. In pull/128, there are two reductions: one in the NTT and one in the poly_tobytes. Due to the stack optimizations that are not described in the specification of Kyber/ML-KEM, the output of NTT should be mapped to [0, q) while packing the elements to the public key array. This remains until pull/244 removed the reduction in the NTT (and counted as a contribution of their paper).
I encountered mismatched testvectors while generating with my own chacha20 for the randombytes and iterating with 5 iterations for all the parameter sets of ml-kem. The mismatched testvectors occurred only on the 5th iteration of ml-kem768.
I don't know what's the plan of the randombytes, so I only applied minimal changes to the files under crypto_kem.
Assembly optimized subroutines and detailed documentations will appear in the future.