summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/man/X509_new.3 (follow)
Commit message (Collapse)AuthorAgeFilesLines
* 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
* finish crypto HISTORY; mostly 1.1.0/6.3, but also various other fixesschwarze2018-03-231-1/+5
|
* crypto HISTORY up to 1.0.2; researched from OpenSSL git and OpenBSD CVSschwarze2018-03-231-2/+6
|
* x509.h HISTORY up to SSLeay 0.8.1b; researched from OpenSSL gitschwarze2018-03-211-3/+4
|
* In x509.h rev. 1.41 2018/02/22 17:22:02, jsing@ providedschwarze2018-02-261-6/+31
| | | | | X509_chain_up_ref(3). Merge the documentation from OpenSSL, tweaked by me.
* Consistently mark up various ASN.1 type names defined in standardsschwarze2016-12-251-4/+5
| | | | 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
|
* Link to Peter Gutmann's classic "X.509 Style Guide".schwarze2016-12-231-2/+11
| | | | | | | | | | Thanks to otto@ for making me aware of it. If people know newer documents that are similarly readable and interesting, please speak up. I hate sending people to the STANDARDS only for more information. On the one hand, that's torture, and on the other hand, if i read Gutmann correctly, the standards sometimes provide bad advice, and often none at all.
* Delete the x509(3) manual page and merge what little content remainedschwarze2016-12-221-9/+26
| | | | into X509_new(3). Add information about STANDARDS.
* various cleanup;jmc2016-12-121-3/+3
|
* tweak previous;jmc2016-12-051-2/+3
|
* Add Copyright and license.schwarze2016-12-051-5/+69
| | | | Merge documentation of X509_up_ref(3) from OpenSSL.
* various cleanup;jmc2016-12-031-4/+4
|
* first pass; ok schwarzejmc2016-11-061-1/+3
|
* convert X509 manuals from pod to mdocschwarze2016-11-041-0/+49