summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/man/X509_VERIFY_PARAM_set_flags.3 (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Remove most documentation pertaining to proxy certificates.tb2023-04-301-2/+4
| | | | | Update EXFLAG_PROXY and X509_V_FLAG_ALLOW_PROXY_CERTS documentation since we need to keep them for the time being.
* The policy tree is no moretb2023-04-301-4/+2
| | | | | Mop up documentation mentioning it or any of its numerous accessors that almost nothing ever used.
* Mark the X509_V_FLAG_CB_ISSUER_CHECK flag as deprecatedtb2022-12-011-11/+5
|
* In x509_vfy.h rev. 1.54, tb@ provided X509_VERIFY_PARAM_get_time(3)schwarze2022-07-131-3/+44
| | | | | | and X509_VERIFY_PARAM_set_auth_level(3). Document them. For the latter, i included a few sentences from the OpenSSL 1.1.1 branch, which is still under a free license.
* man pages: add missing commas between subordinate and main clausesnaddy2022-03-311-4/+4
| | | | | | | jmc@ dislikes a comma before "then" in a conditional, so leave those untouched. ok jmc@
* man pages: add missing commas in enumerationsnaddy2022-03-291-3/+3
|
* unsusual -> unusualjsg2022-03-101-3/+3
|
* deafult -> defaultjsg2021-12-311-3/+3
|
* In x509_vfy.h rev. 1.37 and x509_vfy.c rev. 1.91, tb@ providedschwarze2021-11-171-2/+4
| | | | | | | | | | | | | | | | | X509_STORE_CTX_set_verify(3) and X509_STORE_CTX_get_verify(3). Document them. In the next bump, tb@ will also provide X509_STORE_CTX_verify_fn(3) and X509_STORE_set_verify(3) and restore X509_STORE_set_verify_func(3) to working order. For efficiency of documentation work, already document those three, too, but keep the text temporariy .if'ed out until they become available. Delete X509_STORE_set_verify_func(3) from X509_STORE_set_verify_cb_func(3) because it was misplaced in that page: it is not related to the verification callback. tb@ agrees with the general direction.
* Document the interactions of X509_V_FLAG_USE_CHECK_TIME,schwarze2021-11-131-6/+35
| | | | | | | | X509_V_FLAG_NO_CHECK_TIME, X509_VERIFY_PARAM_set_time(3), X509_VERIFY_PARAM_set_flags(3), and X509_VERIFY_PARAM_clear_flags(3) in detail because the API design is both surprising and surprisingly complicated in this respect, and the resulting nasty traps have already caused bugs in the past.
* Document the public constants X509_V_FLAG_POLICY_MASKschwarze2021-11-121-9/+43
| | | | | | | and X509_V_FLAG_USE_CHECK_TIME. While here, fix a typo and improve the wording for X509_V_FLAG_NOTIFY_POLICY.
* split seven functions out of the page X509_VERIFY_PARAM_set_flags(3), whichschwarze2021-10-181-129/+9
| | | | | is becoming excessively long, into a new page X509_VERIFY_PARAM_new(3); no content change
* clarify the meaning of the argument of X509_VERIFY_PARAM_set_purpose(3)schwarze2021-07-231-10/+16
|
* space between RFC and number;jmc2021-06-111-3/+3
|
* Install the new page SSL_set1_host(3), link to it from relevant places,schwarze2020-09-171-4/+5
| | | | | | | and add two other .Xrs that might help readers find their way. Update the merge notices of all files touched and merge a few trivial changes from the OpenSSL 1.1.1 branch. OK tb@
* tweak previous;jmc2018-04-071-8/+8
|
* poison for X509_VERIFY_PARAM'sbeck2018-04-061-14/+53
| | | | | | | | | | | | Tighten up checks for various X509_VERIFY_PARAM functions, and allow for the verify param to be poisoned (preculding future successful cert validation) if the setting of host, ip, or email for certificate validation fails. (since many callers do not check the return code in the wild and blunder along anyway) Inspired by some discussions with Adam Langley. ok jsing@
* crypto HISTORY up to 1.0.2; researched from OpenSSL git and OpenBSD CVSschwarze2018-03-231-1/+15
|
* crypto HISTORY up to 0.9.8h; researched from OpenSSL gitschwarze2018-03-231-2/+7
|
* crypto HISTORY up to 0.9.8; researched from OpenSSL gitschwarze2018-03-231-2/+20
|
* In x509_vfy.h rev. 1.24 2018/02/22 17:19:31, jsing providedschwarze2018-02-251-2/+5
| | | | | | | | X509_STORE_get0_objects(3). Merge the documenteation from OpenSSL, heavily tweaked by me. While here, document six additional public functions closely related to X509_STORE_set1_param(3) that OpenSSL lacks documentation for. No Copyright-worthy amount of text remains in X509_STORE_set1_param.3, so switch to my Copyright and license.
* Remove a warning about the dangers of X509_VERIFY_PARAM_set1_name(3)schwarze2018-02-171-5/+2
| | | | | | because jsing@ points out that this follows a (dangerous) general pattern in the library, and mentioning that everywhere would become repetitive.
* Document three more functions recently made public by jsing@schwarze2018-02-111-18/+185
| | | | | | as requested by jsing@, and also document six more related functions that have already been public before that. OpenSSL fails to document any of these.
* Merge documentation from OpenSSL for seven functionsschwarze2018-02-111-7/+196
| | | | | that jsing@ recently exposed publicly in libcrypto. Requested by jsing@.
* Delete a sentence containing a cross reference to an undocumentedschwarze2017-01-061-6/+2
| | | | | | | function that had the the sole purpose of discouraging its use. Not talking about it at all discourages using it even more. Dangling cross reference reported by jmc@.
* Copyright and licenseschwarze2016-12-051-2/+50
|
* various cleanup;jmc2016-12-031-9/+9
|
* first pass; ok schwarzejmc2016-11-061-1/+3
|
* convert X509 manuals from pod to mdocschwarze2016-11-041-0/+271