summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/man/X509_new.3 (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Remove X509_check_trust documentationtb2024-09-021-3/+2
|
* Remove docs of various X509_TRUST "functionality" that no longer existstb2024-08-171-3/+2
| | | | | | | Some macros are still exposed, but apart from the loss of a very nice way of saying "this is completely misdesigned, overengineered and not properly thought through" the only thing we would have learned from it is that this stuff is "probably useless".
* Document X509v3_{addr,asid}_validate_{path,resource_set}(3)tb2023-09-291-2/+3
| | | | | | | These were the last four RFC 3779 things that check_complete.pl x509v3 complained about. I will surely tweak and try to improve a few things in the coming days, but the pages should now be stable enough that review efforts will likely not be wasted. Any feedback appreciated.
* Document X509v3_{addr,asid}_subset.3tb2023-09-281-2/+3
| | | | | | First RFC 3779 page without a BUG section. It could have one, but I'm in a lenient mood right now. Maybe it's just that this is bad but not quite as bad as EVP.
* Document X509v3_{addr,asid}_inherits(3)tb2023-09-261-1/+3
| | | | Also note another bug in X509v3_asid_{canonize,is_canonical}(3).
* Document the guts of RFC 3779 IPAddrBlockstb2023-09-261-2/+3
| | | | Let's just say there's room for improvement...
* New manual page documenting the usual four ASN.1 functions for bothtb2023-09-251-1/+2
| | | | ASRange and ASIdOrRange
* Add initial documentation for the RFC 3779 APItb2023-09-251-3/+6
| | | | | | | | This documents the part of the API that allows building the two extensions. It is all very complicated and the bug density is quite high. Surely there's lots of room for improvement, but I've been sitting way too long on versions of these. I'll never finish. Let's fix and improve in tree.
* The policy tree is no moretb2023-04-301-4/+2
| | | | | Mop up documentation mentioning it or any of its numerous accessors that almost nothing ever used.
* In x509_vfy.h rev. 1.35 and x509_lu.c rev. 1.34, tb@ providedschwarze2021-11-181-2/+3
| | | | | | | | X509_OBJECT_new(3) and X509_OBJECT_free(3); document them. While here, stop talking about storing storing EVP_PKEY objects and plain C strings in X509_OBJECT objects. LibreSSL never fully supported that, and it certainly no longer supports that now.
* Split a new page X509_load_cert_file(3) with three functionsschwarze2021-11-091-2/+3
| | | | | | | | | | | | | | | out of X509_LOOKUP_hash_dir(3) because both groups of functions differ substantially in purpose and structure. Rewrite the complete text of X509_load_cert_file(3) from scratch for correctness and clarity. This fixes several documentation errors: 1. The names of the constants were wrong, lacking the "X509_" prefix. 2. None of these functions support X509_FILETYPE_DEFAULT, neither in OpenSSL nor in LibreSSL. 3. The memory cache does not contain X509_STORE objects; instead, the X509_STORE object *is* the memory cache.
* document X509_REQ_to_X509(3)schwarze2021-10-281-7/+38
|
* add some .Xrs involving recently added pagesschwarze2021-10-271-2/+3
|
* document X509_get_pubkey_parameters(3) in a new manual pageschwarze2021-10-191-1/+2
|
* document X509_PKEY_new(3) and X509_PKEY_free(3)schwarze2021-10-191-2/+3
|
* new manual page X509_STORE_get_by_subject(3)schwarze2021-08-021-2/+3
|
* document X509_LOOKUP_mem(3) in X509_LOOKUP_hash_dir(3)schwarze2021-07-311-2/+4
| | | | and add a new manual page X509_LOOKUP_new(3)
* new manual page X509_policy_check(3)schwarze2021-07-271-2/+3
|
* new manual page X509_policy_tree_level_count(3)schwarze2021-07-261-2/+3
| | | | documenting the X509_POLICY_TREE object and its sub-objects
* Two new manual pages X509_TRUST_set(3) and X509_check_trust(3)schwarze2021-07-241-3/+5
| | | | | documenting ten functions related to X509_TRUST objects, trust identifiers, and trust indices.
* new manual page X509_PURPOSE_set(3) documenting 11 functionsschwarze2021-07-231-2/+3
| | | | related to X509_PURPOSE objects, purpose identifiers, and purpose indices
* new manual page X509_print_ex(3)schwarze2021-07-121-2/+3
|
* document X509_find_by_subject(3) and X509_find_by_issuer_and_serial(3)schwarze2021-07-041-2/+3
|
* document X509_get1_email(3), X509_get1_ocsp(3), X509_email_free(3)schwarze2019-08-231-1/+2
|
* document X509_dup(3)schwarze2019-08-231-8/+40
|
* document X509_check_purpose(3)schwarze2019-08-221-2/+3
|
* 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.
* document X509_INFO_new(3) and X509_INFO_free(3)schwarze2019-08-191-7/+3
|
* delete references to ERR pages from SEE ALSO where suchschwarze2019-06-101-3/+2
| | | | references were already given below RETURN VALUES right above
* Tree structure for manual pages: crypto(3) links to 33 functionschwarze2019-06-061-3/+22
| | | | | | | | | | | 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@
* 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
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-04-29 07:18:22 +0000