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

	Commit message (Collapse)	Author	Age	Files	Lines
*	mlkem regress: garbage collect two global variables	tb	2024-12-20	1	-4/+1
\|
*	Fix whitespace in Makefile	tb	2024-12-20	1	-22/+22
\|
*	That works better with a G	tb	2024-12-20	1	-2/+2
\|
*	cant't -> can't	tb	2024-12-20	10	-20/+20
\| \| \| \|	(the mystery of spotting typos right after commit strikes again)
*	Rework and fix the mlkem tests	tb	2024-12-20	16	-997/+1824
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Make proper use of CBB and CBS. If a CBS ever owns data, you're holding it wrong. Ditch gross macros, sscanf, and globals. The use of fgets is annoying here, so replace it with getline, which be provided by portable if needed. Most importantly, make the tests actually signal failure rather than only printing an error. Fix the state machines in a few of them. Some tests didn't parse the .txt file at all. Others mostly did but didn't actually test what they were supposed to be testing. Such failures were hidden by the way the tests were written. This basically needed a complete revamp. It still isn't pretty and much of it could be deduplicated, but I only have so much time alotted on this blue planet.
*	mlkem regress: reach around into bytestring again	tb	2024-12-19	1	-1/+2
\|
*	Close fp before exit since we clean up other stuff	tb	2024-12-17	4	-4/+8
\| \| \| \|	From Kenjiro Nakayama
*	Plug leak coming from debug leftover	tb	2024-12-17	2	-4/+2
\| \| \| \|	There's still CBS holding data in here. Yuck.
*	Stop reaching into libcrypto/bytestring	tb	2024-12-14	1	-2/+1
\|
*	Normalize top of files	tb	2024-12-14	15	-109/+138
\| \| \| \|	RCS marker, KNF for comment, fix and sort includes as usual.
*	Add ML-KEM 1024 from BoringSSL	beck	2024-12-13	13	-3/+5262
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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.
*	Add ML-KEM 768 from BoringSSL	beck	2024-12-13	15	-0/+5424
	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.