summaryrefslogtreecommitdiff
path: root/src/regress/lib/libcrypto/bn/Makefile (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Add initial regress for BN_set_bit(), BN_clear_bit() and BN_mask_bits().jsing2024-04-091-1/+2
|
* The bn_mod_exp test is no longer an expected failuretb2023-10-191-3/+1
|
* Add test case checking aliasing of the result with other argumentstb2023-10-191-1/+3
| | | | | These are expected failures for BN_mod_exp_simple() and the internal BN_mod_exp_recp(), which will be fixed shortly.
* Retire the bn_rand_interval() testtb2023-08-031-3/+1
| | | | | | This test was never particularly useful. An upcoming API change for the internal bn_rand_interval() API would require some adjustments. It's not worth it.
* Add regress coverage for bn_printftb2023-07-061-1/+3
| | | | | This must be one of the ugliest tests I've ever written, but I can't think of a better way of doing it.
* Add regress coverage for BN_mod_inverse()tb2023-06-031-1/+2
| | | | | This would detect the aliasing issue reported by Guido Vranken fixed in bn_gcd.c r1.28. Most testcases are from BoringSSL's regress test.
* Provide initial regress for BN_{asc,dec,hex}2bn()/BN_bn2{dec,hex}()jsing2023-04-221-1/+2
|
* Allow overriding the bc implementation used in run-bctb2023-04-171-2/+7
| | | | | | | | | | | | While base bc is great, it uses libcrypto's BIGNUM implementation. This implies that the independent verification of the bn_test isn't as independent as it should be. With this commit, run-bc picks up bn-gh if it is installed. This appears to work on amd64, arm64 and sparc64 (where gbc is busted). I will send PRs to the regress maintainers once I will have tested this a bit more thoroughly. Committing this early since I juggle way too many diffs already.
* Fix typotb2023-04-171-2/+2
|
* Provide benchmarks for BN_copy()jsing2023-04-101-1/+2
|
* bn_to_string no longer needs to be linked staticallytb2023-04-101-2/+1
|
* Link bn_gcd test to regresstb2023-04-031-1/+3
|
* Unhook bn_mod_exp2_mont testtb2023-03-261-2/+1
|
* bn_primes: there is no need to link this statically. It can pull thetb2023-03-261-2/+5
| | | | primes table in directly.
* Rename bn_mod_exp_zero to the more appropriate bn_mod_exptb2023-03-181-3/+3
|
* Retire the bn_mod_exp test.tb2023-03-181-3/+1
| | | | Its is fully covered by bn_mod_exp_zero now.
* Add regress coverage for BN_{add,sub,mul,div,mod}_word().jsing2023-03-111-1/+2
| | | | | | | This also provides some indirect coverage for BN_hex2bn(), BN_bn2hex() and BN_get_word(). Two of these tests are currently failing and will be fixed shortly.
* Add bn/arch/${MACHINE_CPU} to the include path.jsing2023-01-311-1/+2
| | | | This will be needed once headers pull in bn_arch.h.
* Rename bn_mul.c regress to bn_mul_div.c.jsing2023-01-291-4/+4
|
* Provide basic benchmarks for BN_mul() and BN_sqr().jsing2023-01-211-2/+4
|
* Move benchmark target up a bit and mark it phonytb2022-12-171-4/+5
|
* Provide regress coverage for BN shift functions.jsing2022-12-171-1/+5
| | | | | | Provide regress coverage for BN_lshift1(), BN_rshift1(), BN_lshift() and BN_rshift(), along with basic benchmarking functionality (run via 'make benchmark').
* bn/Makefile: tidy up and simplifytb2022-12-091-16/+10
|
* Link new bn_mod_exp_zero test to buildtb2022-12-021-1/+3
|
* libcrypto/bn: switch back to manual regress targetstb2022-12-021-3/+8
| | | | | The previous change had the undesired side effect of running the super verbose run-regress-bn_test.
* Use the default targets from bsd.regress.mk as far as possibletb2022-12-021-9/+4
|
* Fix typo, move one .PHONY target nearer to the target itselftb2022-12-011-4/+3
|
* zap extra blank linetb2022-12-011-2/+1
|
* Check that the bn_isqrt -C output isn't changedtb2022-12-011-1/+13
| | | | | | bn_isqrt -C generates code included in lib/libcrypto/lib/bn_isqrt.c. The regress tests already ensure that the content of the tables don't change. Ensure further that the code generation doesn't get out of sync.
* regress/libcrypto: merge exp/ into bn/tb2022-12-011-1/+3
| | | | | | | Move exp/exptest.c to bn/bn_mod_exp.c. This is a BN test that mostly tests a variety of BN_mod_exp*() API behavior and correctness. Commit stolen from jsing
* Flatten structure of libcrypto/bn teststb2022-12-011-14/+52
| | | | | | | | | The bn tests were distributed into three subdirectories rather randomly. It's cleaner and easier to maintain if all this is in a single directory. Use consistent names for the .c files, unify handling of the tests with the exception of bn_test, which is special. Discussed with jsing
* Add regress coverage for BN_cmp()/BN_ucmp().jsing2022-11-301-3/+11
| | | | | Some tests current fail due to a bug in BN_ucmp(), which will be fixed soon.
* link rand/ to buildtb2018-11-061-2/+4
|
* +addsubtb2018-07-101-1/+2
|
* Simple regress test for the amd64 bn_mul_mont bug found by Joyentmiod2014-06-201-2/+3
| | | | | ( https://github.com/joyent/node/issues/7704 ), about to be fixed in libcrypto.
* Move the crypto/bn regression test one directory deeper in preparation formiod2014-06-201-7/+6
| | | | it getting siblings.
* Build these tests with WARNINGS=Yes and -Werror, and do the necessarymiod2014-06-011-1/+3
| | | | fixes to keep building.
* Import the OpenSSL libcrypto tests in a form suitable for our rergressmiod2014-04-151-0/+7
infrastructure. The following tests have not been imported, for their code lacks a licence: asn1, rsa, sha256, sha512, wp.