typos: us -> is, te -> the (twice)
Do not assume mlkem.h and bytestring.h are public in libcrypto
As long as is not quite clear what we want to do about the public API
aspect of MLKEM, keep things internal for now.
discussed with beck and jsing
mlkem: clean up top matter in headers
OpenBSD/src mkRFVnD — lib/libcrypto/mlkem mlkem1024.c, regress/lib/libcrypto/mlkem mlkem1024_encap_tests.txt mlkem1024_decap_tests.txt
Add ML-KEM 1024 from BoringSSL
Changes include conversion from C++, basic KNF, then adaptation to
use our sha3 functions for sha3 and shake instead of the BorinSSL
version. This Adds units tests to run against BoringSSL and NIST test
vectors.
The future public API is the same as Boring's - but is not yet exposed
pending making bytestring.h public (which will happen separately) and
a minor bump
Currently this will just ensure we build and run regress.
ok tb@ to get it into the tree and massage from there.
OpenBSD/src omGKPmv — lib/libcrypto/mlkem mlkem768.c mlkem.h, regress/lib/libcrypto/mlkem mlkem768_encap_tests.txt mlkem768_decap_tests.txt
Add ML-KEM 768 from BoringSSL
Changes include conversion from C++, basic KNF, then adaptation to
use our sha3 functions for sha3 and shake instead of the BorinSSL
version. This Adds units tests to run against BoringSSL and NIST test
vectors.
The future public API is the same as Boring's - but is not yet exposed
pending making bytesring.h public (which will happen separately) and
a minor bump
Currently this will just ensure we build and run regress.
ok tb@ to get it into the tree and massage from there.
