openbsd/src/regress/lib/libcrypto/Makefile, branch OPENBSD_7_0_BASEA mirror of https://github.com/libressl/openbsd.git
https://git.lua4.win/openbsd/atom?h=OPENBSD_7_0_BASE2020-12-26T00:48:56+00:00Convert CA regress implementation from shell script to make file.2020-12-26T00:48:56+00:00bluhm2020-12-26T00:48:56+00:00urn:sha1:80f33da71cc6d1cbd2c0114d03a2d2c25c8d4029
Ensure that it works with obj directory and link regress to build.
hook symbols test to regress2020-09-18T10:19:31+00:00tb2020-09-18T10:19:31+00:00urn:sha1:7e60f46978a7f69c6f9cf1c654e23d1e79621db5Fix a bug in PEM_X509_INFO_read_bio(3) that is very likely to cause2020-07-23T17:15:35+00:00schwarze2020-07-23T17:15:35+00:00urn:sha1:bc9c51cf66fc92815074622c1c64a0e8bd9d5796
use-after-free and double-free issues in calling programs.
The bug was introduced in SSLeay-0.6.0 released on June 21, 1996
and has been present since OpenBSD 2.4.
I found the bug while documenting the function.
The bug could bite in two ways that looked quite different from the
perspective of the calling code:
* If a stack was passed in that already contained some X509_INFO
objects and an error occurred, all the objects passed in would be
freed, but without removing the freed pointers from the stack,
so the calling code would probable continue to access the freed
pointers and eventually free them a second time.
* If the input BIO contained at least two valid PEM objects followed by
at least one PEM object causing an error, at least one freed pointer
would be put onto the stack, even though the function would return NULL
rather than the stack. But the calling code would still have a pointer
to the stack, so it would be likely to access the new bogus pointers
sooner or later.
Fix all this by remembering the size of the input stack on entry
and cutting it back to exactly that size when exiting due to an
error, but no further.
While here, do some related cleanup:
* Garbage collect the automatic variables "error" and "i"
which were only used at one single place each.
* Use NULL rather than 0 for pointers.
I like bugfixes that make the code four lines shorter, reduce the
number of variables by one, reduce the number of brace-blocks by
one, reduce the number if if-statements by one, and reduce the
number of else-clauses by one.
Tweaks and OK tb@.
Enter the certs regress directory.2020-07-14T18:33:34+00:00jsing2020-07-14T18:33:34+00:00urn:sha1:54e6b184aac6eaf631e6f6ae7d8089bd18cf3adeHook cms regress.2019-11-02T15:39:44+00:00jsing2019-11-02T15:39:44+00:00urn:sha1:c0ba598a93a628e61c5356c0f188fcbc8ca88bd6link sm4 regress to the build2019-03-17T17:49:12+00:00tb2019-03-17T17:49:12+00:00urn:sha1:895f4a322c4e322f1afc38c2b7acfa2c155fd5f8Hook up sm3 regress tests.2018-11-11T07:13:03+00:00tb2018-11-11T07:13:03+00:00urn:sha1:7764588e715807e7cae26bdca8c05b043f300de4The Botan library from ports an be configured to use OpenSSL or2018-11-09T23:44:32+00:00bluhm2018-11-09T23:44:32+00:00urn:sha1:450faf95322d31d1696e4721ab1bcfeee092abbf
LibreSSL as crypto provider. When we run their regression tests,
we are actually testing our library. This is far from perfect. A
lot of LibreSSL features have not been implemented as Botan provider.
Even if provider openssl is specified, botan-test runs a lot of
non-openssl tests. This can be improved later.
Add subdirectires with SUBDIR += instead of a single assignment with2018-11-09T19:24:50+00:00tb2018-11-09T19:24:50+00:00urn:sha1:14d1b12c76ae17b63d5368e647a5bca9e82fc390
line continuations.
Provide a harness that runs test vectors from Project Wycheproof against2018-07-25T18:04:09+00:00jsing2018-07-25T18:04:09+00:00urn:sha1:189c1bbc6125d0d98703fd813fa538e8ce71e754
libcrypto. Initially this just covers RSA signatures, but can be extended
to cover other cryptographic algorithms.
This regress requires the go and wycheproof-testvector packages to be
installed, with the regress being skipped otherwise.
Discussed with beck@ and tb@