summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/man/X509_NAME_new.3 (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Split X509_NAME_hash(3) out of d2i_X509_NAME(3) and documentschwarze2021-07-201-2/+3
| | | | | | | | | | X509_issuer_name_hash(3), X509_subject_name_hash(3), and the _old variants. Even though this is only tangentially related to decoding and encoding, including a single function in d2i_X509_NAME(3) was probably OK, but let's not bog down that page with six functions that are likely to become obsolete at some point - even though right now, they are still being used both internally and by external software.
* New manual page X509_cmp(3) documenting the same public functionsschwarze2019-08-201-2/+3
| | | | | | as in OpenSSL 1.1.1. I rewrote most of the text for clarity, precision, and conciseness and added some additional information. A few sentences from Paul Yang remain.
* Tree structure for manual pages: crypto(3) links to 33 functionschwarze2019-06-061-3/+5
| | | | | | | | | | | group pages, and these link on to all their second-level subpages. Only a handful of second-level pages have third-level subpages. So all crypto pages can now be reached from the www.libressl.org frontpage via at most four clicks, in most cases three clicks. Also link back from leaf pages to their respective group pages and add a couple of additional links between related pages. Triggered by a question from deraadt@. OK jmc@ tb@
* Document that X509_{NAME,REQ,REQ_INFO}_free() are all NULL safe.tb2018-07-291-2/+7
| | | | From Ross L. Richardson
* found a complete archive of SSLeay-0.4 to SSLeay-0.8.1b tarballsschwarze2018-03-271-3/+3
| | | | on the web, so fix up SSLeay HISTORY accordingly
* x509.h HISTORY up to SSLeay 0.8.1b; researched from OpenSSL gitschwarze2018-03-211-2/+8
|
* Consistently mark up various ASN.1 type names defined in standardsschwarze2016-12-251-6/+11
| | | | related to X.509 with .Vt such that they can be searched for.
* sprinkle some cross references to newly written x509v3 manual pagesschwarze2016-12-241-2/+4
|
* Write X509_NAME_new(3) manual from scratch. Both functions areschwarze2016-12-141-0/+81
listed in <openssl/x509.h> and in OpenSSL doc/man3/X509_dup.pod. Note that the OpenSSL documentation specifies the wrong header file.