Spencer Wilson
Spencer Wilson
Thanks for the report. Is it accurate to say that this is something that should ideally be fixed upstream? (i.e., in https://github.com/pq-crystals/kyber for this example)
Looping @hanno-becker @mkannwischer @praveksharma: Does mlkem-native implement these protections?
Even when the updated mlkem-native implementation lands, this check will still likely fail due to assembly files in other algorithms (e.g., McEliece). However, if we could get it to run...
> Not really: Please note the presence of `-DOQS_ALGS_ENABLED=NIST` above. Hence, the above won't be a problem -- as long as the new CI test also IMO primarily targets (only?)...
I tried to duplicate this test now that the mlkem-native implementation has been updated. I observed something weird in the process: - After the initial configure and build commands, the...
ML-KEM private keys not compatible with draft-ietf-lamps-kyber-certificates-06 (seed as private key)
Reading the draft, I'm only seeing one place that specifies a short private key: the example in Appendix C.2. This was changed less than a month ago; previously the example...
ML-KEM private keys not compatible with draft-ietf-lamps-kyber-certificates-06 (seed as private key)
> @SWilson4 the IETF LAMPS consensus is that private keys of all three of the NIST algorithms should be stored as seeds, not as expanded keys, for the private key...
Hi @anhu! I believe you need to upgrade OpenSSL to [at least 3.2](https://github.com/open-quantum-safe/oqs-provider?tab=readme-ov-file#3031) in order to use post-quantum signatures. Please let me know if that solves the problem for you.
@anhu It works for me in a fresh Ubuntu 24 Docker container. Did the script complete successfully?
Looping in @alexrow and @rtjk as the maintainers of CROSS.