summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/man/X509_check_purpose.3 (follow)
Commit message (Collapse)AuthorAgeFilesLines
* This commit was manufactured by cvs2git to create tag 'tb_20250414'.tb_20250414cvs2svn2025-04-141-431/+0
|
* Remove X509_check_trust documentationtb2024-09-021-3/+2
|
* Adjust/fix X509_check_purpose(3) documentationtb2023-06-251-3/+3
|
* The policy tree is no moretb2023-04-301-3/+2
| | | | | Mop up documentation mentioning it or any of its numerous accessors that almost nothing ever used.
* X509_check_purpose.3: incorporate feedback from jsingtb2022-12-171-5/+5
|
* Document extension caching of X509_check_purpose()tb2022-12-161-23/+43
| | | | | | | | | | The overwhelming majority of callers of X509_check_purpose() in our tree pass a purpose of -1. In this case X509_check_purpose() acts as a wrapper of x509v3_cache_extensions() which makes sanity checks like non-negativity of ASN.1 integers or canonicity of RFC 3779 extensions as well as checking uniqueness of extensions. from schwarze who beat an initial diff of mine into shape
* In x509/x509_purp.c rev. 1.11, tb@ fixed X509_check_purpose(3)schwarze2021-10-291-8/+18
| | | | | | to fail if parsing of a certificate extension failed. Adjust the documentation accordingly. OK tb@
* new manual page X509_policy_check(3)schwarze2021-07-271-2/+3
|
* Two new manual pages X509_TRUST_set(3) and X509_check_trust(3)schwarze2021-07-241-2/+3
| | | | | documenting ten functions related to X509_TRUST objects, trust identifiers, and trust indices.
* mention the possibility that user-defined purpose identifiers may haveschwarze2021-07-231-2/+13
| | | | been defined or user-supplied checking functions may have been installed
* new manual page X509_PURPOSE_set(3) documenting 11 functionsschwarze2021-07-231-2/+3
| | | | related to X509_PURPOSE objects, purpose identifiers, and purpose indices
* space between macro args and punctuation;jmc2021-06-121-3/+3
|
* document X509_check_purpose(3)schwarze2019-08-221-0/+389