openbsd/src/regress/lib/libcrypto/mlkem, branch OPENBSD_7_7_BASEA mirror of https://github.com/libressl/openbsd.git
https://git.lua4.win/openbsd/atom?h=OPENBSD_7_7_BASE2024-12-29T20:14:15+00:00Zap extraneous -DLIBRESSL_INTERNAL2024-12-29T20:14:15+00:00tb2024-12-29T20:14:15+00:00urn:sha1:aa15a66ebefe418b5551c377b2da39331f760455parse test file: add helper to skip to end of line2024-12-27T11:17:48+00:00tb2024-12-27T11:17:48+00:00urn:sha1:c0ac38c8c9e36d18575006b55c8e70e3ab70978cFix the unittest with Emscripten2024-12-26T12:35:25+00:00tb2024-12-26T12:35:25+00:00urn:sha1:6e018de4bbd1349c71547b01c7f6830b5662c240
Split main into two helper functions since having a few ML-KEM key blobs
on the stack makes Emscripten's stack explode, leading to inscrutable
silent failures unles ASAN is enabled. Go figure.
mlkem iteration test: drop extraneous typedef2024-12-26T07:26:45+00:00tb2024-12-26T07:26:45+00:00urn:sha1:2ad04cc9b4219898646f4409abfc0b784c5a6300mlkem tests: whitespace tweak and fix an error message2024-12-26T05:51:41+00:00tb2024-12-26T05:51:41+00:00urn:sha1:546cd0008caa2bf86b5c9d42fca48651bb76286bfat fingers2024-12-26T00:10:19+00:00tb2024-12-26T00:10:19+00:00urn:sha1:79cebeb3fc776b541d6c72772bf811986b7c4c42Overhaul ML-KEM regress once more2024-12-26T00:04:24+00:00tb2024-12-26T00:04:24+00:00urn:sha1:4842526a7c0b4e205e8f4080c330cbf7130a758b
Implement a file parser that drives a state machine to extract the test data
from the .txt files and manages the parsed data. Comments and empty lines are
ignored. The code currently assumes that instruction lines are at the start
of the file (which isn't generally true) and only supports two line types for
now. This is good enough for all the ML-KEM tests but should be easy enough
to extend.
Once all data for a test case is parsed in the expected order, a test handler
is called which can retrieve the test data via a simple API and throw warnings
and errors with information on the test case line number, etc.
Merge the tests into three programs: one parsing the .txt files and running
the corresponding test cases, a unit test and the iteration tests. Deduplicate
the actual test code and let the caller pass in an object containing the
API functions, private keys and arrays that need to be different between the
768 version and the 1024 version. This way we don't have two sets of half a
dozen .c files differing only in 3 or 4 occurrences of 768 and 1024.
All this will also make it a lot easier to hook these tests into portable.
mlkem regress: garbage collect two global variables2024-12-20T15:47:26+00:00tb2024-12-20T15:47:26+00:00urn:sha1:a25b848bafc0c3ba6f641502653c50599b747142Fix whitespace in Makefile2024-12-20T01:53:46+00:00tb2024-12-20T01:53:46+00:00urn:sha1:1a23f1617a6ecfd04ad081af8bec4aa39c178d05That works better with a G2024-12-20T01:51:27+00:00tb2024-12-20T01:51:27+00:00urn:sha1:bb183948611b2a58770ddf12de3bcd91a8b7ff60