summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/man/Makefile
diff options
context:
space:
mode:
authorschwarze <>2016-11-27 20:40:07 +0000
committerschwarze <>2016-11-27 20:40:07 +0000
commit2613b464a5e73671df478b07cbb7bb84c6ceea0d (patch)
tree37809d727204ff4a84215c775599f31426aed275 /src/lib/libcrypto/man/Makefile
parent9dfb65eab2197f3d5d42b3a11527c846bb6c584c (diff)
downloadopenbsd-2613b464a5e73671df478b07cbb7bb84c6ceea0d.tar.gz
openbsd-2613b464a5e73671df478b07cbb7bb84c6ceea0d.tar.bz2
openbsd-2613b464a5e73671df478b07cbb7bb84c6ceea0d.zip
Import OCSP documentation from OpenSSL, leaving out some stuff
that we don't have, fixing some bugs and tweaking some parts for readability. P.S. Why did some people write a HTTP client implementation and then decide that the best place to publish it might be a crypto(3) library? Oh never mind, to go easy on my sanity, i should probably stop asking such questions and just document what i find.
Diffstat (limited to 'src/lib/libcrypto/man/Makefile')
-rw-r--r--src/lib/libcrypto/man/Makefile8
1 files changed, 7 insertions, 1 deletions
diff --git a/src/lib/libcrypto/man/Makefile b/src/lib/libcrypto/man/Makefile
index 447c7d23c3..a1cc37cb35 100644
--- a/src/lib/libcrypto/man/Makefile
+++ b/src/lib/libcrypto/man/Makefile
@@ -1,4 +1,4 @@
1# $OpenBSD: Makefile,v 1.55 2016/11/26 18:09:35 schwarze Exp $ 1# $OpenBSD: Makefile,v 1.56 2016/11/27 20:40:07 schwarze Exp $
2 2
3.include <bsd.own.mk> 3.include <bsd.own.mk>
4 4
@@ -122,6 +122,12 @@ MAN= \
122 HMAC.3 \ 122 HMAC.3 \
123 MD5.3 \ 123 MD5.3 \
124 OBJ_nid2obj.3 \ 124 OBJ_nid2obj.3 \
125 OCSP_REQUEST_new.3 \
126 OCSP_cert_to_id.3 \
127 OCSP_request_add1_nonce.3 \
128 OCSP_resp_find_status.3 \
129 OCSP_response_status.3 \
130 OCSP_sendreq_new.3 \
125 OPENSSL_VERSION_NUMBER.3 \ 131 OPENSSL_VERSION_NUMBER.3 \
126 OPENSSL_config.3 \ 132 OPENSSL_config.3 \
127 OPENSSL_load_builtin_modules.3 \ 133 OPENSSL_load_builtin_modules.3 \