diff options
author | schwarze <> | 2021-07-22 14:30:38 +0000 |
---|---|---|
committer | schwarze <> | 2021-07-22 14:30:38 +0000 |
commit | fbd27065ffc27d490c363b3babac8a57cc51ba7a (patch) | |
tree | 8ffc5d1fe1b1ac730149291e978c927f29d91b17 /src/lib/libcrypto/man/OpenSSL_add_all_algorithms.3 | |
parent | adff88ee2a38aece8bcaf0ba0c293488832d928f (diff) | |
download | openbsd-fbd27065ffc27d490c363b3babac8a57cc51ba7a.tar.gz openbsd-fbd27065ffc27d490c363b3babac8a57cc51ba7a.tar.bz2 openbsd-fbd27065ffc27d490c363b3babac8a57cc51ba7a.zip |
Move X509_STORE_CTX_get0_cert(3) to the X509_STORE_CTX_new(3) manual.
OpenSSL documents it in X509_STORE_CTX_get_error(3), but it is
misplaced there. It has nothing to do with accessing status or
error information but merely retrieves a pointer to the certificate
that the users wants to validate. It is a companion function to
X509_STORE_CTX_init(3), X509_STORE_CTX_set_cert(3),
X509_STORE_CTX_get0_store(3), and X509_STORE_CTX_get0_untrusted(3).
While here:
1. Clarify how the new, init, verify, cleanup, and free calls interact,
and who owns the memory involved, because this is all really confusing
from the user perspective.
2. Clarify how X509_STORE_CTX_init(3), X509_STORE_CTX_set_cert(3), and
X509_STORE_CTX_set_chain(3) partially override each other.
3. Move X509_STORE_CTX_set0_untrusted(3) to the proper place because
it is the same as X509_STORE_CTX_set_chain(3).
4. Add a few missing words and improve some wordings.
Diffstat (limited to 'src/lib/libcrypto/man/OpenSSL_add_all_algorithms.3')
0 files changed, 0 insertions, 0 deletions