| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | document OCSP_parse_url(3) | schwarze | 2019-08-27 | 1 | -6/+75 |
| | | |||||
| * | document X509_get1_email(3), X509_get1_ocsp(3), X509_email_free(3) | schwarze | 2019-08-23 | 1 | -4/+5 |
| | | |||||
| * | crypto HISTORY up to 1.0.0; researched from OpenSSL git | schwarze | 2018-03-23 | 1 | -1/+7 |
| | | |||||
| * | crypto HISTORY up to 0.9.8h; researched from OpenSSL git | schwarze | 2018-03-23 | 1 | -2/+9 |
| | | |||||
| * | crypto HISTORY up to 0.9.7; researched from OpenSSL git | schwarze | 2018-03-22 | 1 | -2/+6 |
| | | |||||
| * | fix broken cross references; found with mandoc -Tlint | schwarze | 2017-07-06 | 1 | -3/+3 |
| | | |||||
| * | Delete most references to crypto(3). That page isn't useful enough | schwarze | 2016-12-06 | 1 | -3/+2 |
| | | | | | to be pointed to from random individual pages. | ||||
| * | various cleanup; | jmc | 2016-11-30 | 1 | -15/+7 |
| | | |||||
| * | Import OCSP documentation from OpenSSL, leaving out some stuff | schwarze | 2016-11-27 | 1 | -0/+245 |
| that we don't have, fixing some bugs and tweaking some parts for readability. P.S. Why did some people write a HTTP client implementation and then decide that the best place to publish it might be a crypto(3) library? Oh never mind, to go easy on my sanity, i should probably stop asking such questions and just document what i find. | |||||
