openbsd - A mirror of https://github.com/libressl/openbsd.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	Whitespace nits from tb	beck	2025-05-20	1	-1/+4
\| \| \| \|	ok tb@
*	Fix up MLKEM768_marshal_private_key to not use a passed in CBB	beck	2025-05-19	1	-24/+40
\| \| \| \| \| \| \| \| \| \| \| \|	Even though this should remain internal, make it the same as the public key marshal function, and make the needed fallout changes in regress. This does not yet do the bikeshed of renaming the structure field in the regress ctx, that will wait until a follow on to convert 1024 in a similar manner ok tb@
*	Remove the boringssl if \|\| ideom from mlkem	beck	2025-05-19	1	-17/+23
\| \| \| \|	ok jsing@, joshua@
*	API changes for ML-KEM	beck	2025-05-19	1	-32/+57
\| \| \| \| \| \| \| \| \|	- Get rid of CBB/CBS usage in public api - Make void functions return int that can fail if malloc fails. Along with some fallout and resulting bikeshedding in the regress tests. ok jsing@, tb@
*	CTASSERT that internal pub/priv keys match the sizes exposed in mlkem.h	tb	2025-05-03	1	-1/+5
\| \| \| \| \| \| \|	This will need reworking (especially deduplicating) anyway, but it doesn't hurt now. From Kenjiro Nakayama
*	Fix typo: multipy -> multiply	tb	2025-01-03	1	-9/+9
\| \| \| \| \|	Reflow the comment to avoid some very unfortunate line wraps. "Note that" is like "literally" a bunch of generally useless noise and best omitted.
*	Do not assume mlkem.h and bytestring.h are public in libcrypto	tb	2024-12-19	1	-3/+2
\| \| \| \| \| \| \|	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: fix whitespace	tb	2024-12-18	1	-2/+3
\|
*	Avoid a reduce once that can cause Clang misoptomization.	beck	2024-12-17	1	-11/+27
\| \| \| \| \| \| \| \|	Some versions of Clang compile this to non-constant time code. The fix is adapted from boring. For full details see: https://boringssl-review.googlesource.com/c/boringssl/+/74447 ok tb@
*	Plug two memory leaks in MLKEM*_generate_key_external_entropy()	tb	2024-12-17	1	-1/+3
\| \| \| \| \| \| \|	This needs more thinking. These are void functions that allocate... Left an XXX for now. From Kenjiro Nakayama
*	KNF nit tb wanted me to fix	beck	2024-12-13	1	-2/+4
\|
*	Add ML-KEM 768 from BoringSSL	beck	2024-12-13	1	-0/+1118
	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.