Dimitri John Ledkov

I will re-test this thanks!

@paulidale With c0eb5c57f77c5a158b989285b1344297e0186235 from February 24 which contains d46667284d193ceb3242ebf17422e62b1c837c60 appears to still exhibit the property of calling OS getrandom. Do I need to somehow create an automated github workflow integration...

Ok, I have a more straight forward reproducer, just a set of config options, and then running all the tests shows the issue.

Not sure if changing test/fips.cnf is acceptable, as potentially I am removing a test matrix case of "no SEED-SRC available, yet things should still work with fallback to os-random". I...

I think no-shared-macos is flaky quick test - because the configuration used there, does not use the code changed here.

@paulidale thank you for the review and the tour of the favorite traps =)

For all new submissions, it will likely be the default in practice KEM, thus yes, it is quite critical to support ACVP testing of this. If funding is required, please...

> One clarification. X25519MLKEM768 is not directly approved by SP 800-227. As a technique, the combination is allowed, but the specific protocol uses a non-approved key combiner via SHAKE rather...

[Draft IG D.S - Key Encapsulation Mechanisms\[Oct 14 25\].pdf](https://github.com/user-attachments/files/23283418/Draft.IG.D.S.-.Key.Encapsulation.Mechanisms.Oct.14.25.pdf) Was posted on CMUF forum for comments. Maybe there is conflicting interpretation, or further caveats needed. The industry is deploying TLS...

> Concatenation is an allowed key combiner if all elements of the hybrid scheme are approved. This would not apply to X25519. Many people are trying to ship hybrid schemes...