Add OCSP API test executable
authorBenjamin Kaduk <bkaduk@akamai.com>
Thu, 19 Oct 2017 19:44:10 +0000 (14:44 -0500)
committerBen Kaduk <kaduk@mit.edu>
Sun, 12 Nov 2017 02:03:49 +0000 (20:03 -0600)
commit27da13430bfb3c178716cec10e8d5d6134e54f90
tree2f45957e64653c8bc826be554f0a375e924bd6db
parentce5886dda80b6f60fb30762381506d5c6f2d995c
Add OCSP API test executable

Some of the OCSP APIs (such as the recently added OCSP_resp_get0_signer)
do not really merit inclusion in the ocsp(1) utility, but we should still
have unit tests for them.

For now, only test OCSP_resp_get0_signer(), but it should be easy to
add more tests in the future.

Provide an X509 cert and private key in the test's data directory
to use for signing responses, since constructing those on the fly
is more effort than is needed.

Reviewed-by: Rich Salz <rsalz@openssl.org>
Reviewed-by: Tim Hudson <tjh@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/4573)
test/build.info
test/ocspapitest.c [new file with mode: 0644]
test/recipes/80-test_ocsp.t
test/recipes/80-test_ocsp_data/cert.pem [new file with mode: 0644]
test/recipes/80-test_ocsp_data/key.pem [new file with mode: 0644]