summaryrefslogtreecommitdiff
path: root/src/lib/libc/stdlib/labs.c
diff options
context:
space:
mode:
authortb <>2025-09-08 08:11:49 +0000
committertb <>2025-09-08 08:11:49 +0000
commit731703a848224f9ac266b1a4d87d2d47caf9c57d (patch)
tree99702660ce7c8d74dbe0f9726757ab74634f5fe5 /src/lib/libc/stdlib/labs.c
parent50734a3ae2c1320cf87d475e9d62636b532c8e90 (diff)
downloadopenbsd-731703a848224f9ac266b1a4d87d2d47caf9c57d.tar.gz
openbsd-731703a848224f9ac266b1a4d87d2d47caf9c57d.tar.bz2
openbsd-731703a848224f9ac266b1a4d87d2d47caf9c57d.zip
wycheproof: rework test selection
Since this has grown organically, the test selection has become a weird mix of globs, regexes and test variants and it is hard to reason about what is run and why. Instead, load all the json files from testvectors_v1/ and look at algorithm (almost always available) and test schema to figure out if we support it in libcrypto and the test harness. This separates the logic of the test runner better from the test selection. Also make it a fatal error if we don't explicitly skip an unknown algorithm.
Diffstat (limited to 'src/lib/libc/stdlib/labs.c')
0 files changed, 0 insertions, 0 deletions