| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | X509_check_purpose.3: incorporate feedback from jsing | tb | 2022-12-17 | 1 | -5/+5 |
| | | |||||
| * | Document extension caching of X509_check_purpose() | tb | 2022-12-16 | 1 | -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) | schwarze | 2021-10-29 | 1 | -8/+18 |
| | | | | | | | to fail if parsing of a certificate extension failed. Adjust the documentation accordingly. OK tb@ | ||||
| * | new manual page X509_policy_check(3) | schwarze | 2021-07-27 | 1 | -2/+3 |
| | | |||||
| * | Two new manual pages X509_TRUST_set(3) and X509_check_trust(3) | schwarze | 2021-07-24 | 1 | -2/+3 |
| | | | | | | documenting ten functions related to X509_TRUST objects, trust identifiers, and trust indices. | ||||
| * | mention the possibility that user-defined purpose identifiers may have | schwarze | 2021-07-23 | 1 | -2/+13 |
| | | | | | been defined or user-supplied checking functions may have been installed | ||||
| * | new manual page X509_PURPOSE_set(3) documenting 11 functions | schwarze | 2021-07-23 | 1 | -2/+3 |
| | | | | | related to X509_PURPOSE objects, purpose identifiers, and purpose indices | ||||
| * | space between macro args and punctuation; | jmc | 2021-06-12 | 1 | -3/+3 |
| | | |||||
| * | document X509_check_purpose(3) | schwarze | 2019-08-22 | 1 | -0/+389 |
 |
index : openbsd | |
| A mirror of https://github.com/libressl/openbsd.git |
| summaryrefslogtreecommitdiff |