summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/man/Makefile (follow)
Commit message (Collapse)AuthorAgeFilesLines
* ASN1_{,F,T}BOOLEAN_it and the encoding and decoding API will movetb2022-01-121-2/+1
| | | | | | to internal only soon. Stop documenting them. ok inoguchi jsing
* new manual page OBJ_add_sigid(3)schwarze2021-12-181-1/+2
|
* new manual page OBJ_NAME_add(3)schwarze2021-12-171-1/+2
|
* Move OBJ_create(3) into its own manual pageschwarze2021-12-151-1/+2
| | | | | because OBJ_nid2obj(3) is already long and more functions related to OBJ_create(3) have to be documented.
* new manual page SMIME_text(3)schwarze2021-12-141-1/+2
|
* new manual page SMIME_read_ASN1(3)schwarze2021-12-141-1/+2
| | | | using parts of the text from SMIME_read_CMS(3) and SMIME_read_PKCS7(3)
* new manual page PEM_write_bio_ASN1_stream(3);schwarze2021-12-131-1/+2
| | | | | certainly not perfect, but arguably better than the even terser PEM_write_bio_CMS_stream(3) and PEM_write_bio_PKCS7_stream(3)
* new manual page SMIME_write_ASN1(3);schwarze2021-12-131-1/+2
| | | | still vague in various respects, but it's a start
* new manual pages i2d_ASN1_bio_stream(3) and SMIME_crlf_copy(3)schwarze2021-12-131-1/+3
|
* New manual page providing a rudimentary description of BIO_new_NDEF(3).schwarze2021-12-121-1/+2
| | | | | | | The API surrounding this is so complicated and streaming is so rarely used in practice that describing this in more detail is not a priority right now. The documentation of the wrapper BIO_new_CMS(3) is also rather vague, and BIO_new_PKCS7() isn't described at all so far.
* new manual page ASN1_bn_print(3)schwarze2021-12-081-1/+2
|
* new manual page BIO_f_asn1(3)schwarze2021-11-271-1/+2
|
* new manual page ASN1_NULL_new(3), also documenting ASN1_NULL_free(3)schwarze2021-11-221-1/+2
|
* new manual page a2d_ASN1_OBJECT(3);schwarze2021-11-221-1/+2
| | | | while here, add a few STANDARDS references
* new manual page d2i_ASN1_BOOLEAN(3) also documenting i2d_ASN1_BOOLEAN(3)schwarze2021-11-211-1/+2
|
* new manual page ASN1_BIT_STRING_num_asc(3)schwarze2021-11-191-1/+2
| | | | documenting the three functions using the BIT_STRING_BITNAME structure
* In x509_vfy.h rev. 1.37 and x509_vfy.c rev. 1.91, tb@ providedschwarze2021-11-171-1/+2
| | | | | | | | | | | | | | | | | X509_STORE_CTX_set_verify(3) and X509_STORE_CTX_get_verify(3). Document them. In the next bump, tb@ will also provide X509_STORE_CTX_verify_fn(3) and X509_STORE_set_verify(3) and restore X509_STORE_set_verify_func(3) to working order. For efficiency of documentation work, already document those three, too, but keep the text temporariy .if'ed out until they become available. Delete X509_STORE_set_verify_func(3) from X509_STORE_set_verify_cb_func(3) because it was misplaced in that page: it is not related to the verification callback. tb@ agrees with the general direction.
* new manual page ASN1_BIT_STRING_set(3) documenting four BIT STRING accessorsschwarze2021-11-151-1/+2
|
* document ASN1_PRINTABLE_type(3) and ASN1_UNIVERSALSTRING_to_string(3)schwarze2021-11-151-1/+3
|
* document ASN1_item_pack(3) and ASN1_item_unpack(3)schwarze2021-11-151-1/+2
|
* document i2a_ASN1_STRING(3) and a2i_ASN1_STRING(3)schwarze2021-11-151-1/+2
|
* new manual page X509_policy_tree_get0_policies(3),schwarze2021-11-111-1/+2
| | | | also documenting X509_policy_tree_get0_user_policies(3)
* Split a new page X509_load_cert_file(3) with three functionsschwarze2021-11-091-1/+2
| | | | | | | | | | | | | | | 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.
* new manual pagesschwarze2021-11-071-1/+4
| | | | ASN1_item_digest(3), ASN1_item_sign(3), and ASN1_item_verify(3)
* new manual page X509_CRL_METHOD_new(3)schwarze2021-10-301-1/+2
| | | | documenting five functions to customize CRL handling
* new manual page X509_REQ_print_ex(3),schwarze2021-10-291-1/+2
| | | | also documenting X509_REQ_print(3) and X509_REQ_print_fp(3)
* sorttb2021-10-281-2/+2
|
* new manual page X509_REQ_add_extensions(3)schwarze2021-10-271-1/+2
| | | | documenting six functions for extensions in certification requests
* install X509_get_extension_flags.3 and X509_SIG_get0.3tb2021-10-261-1/+3
|
* new manual page X509_REQ_add1_attr(3) documenting nine functionsschwarze2021-10-261-1/+2
| | | | for X.501 Attributes in PKCS#10 certification requests
* sorttb2021-10-251-17/+17
|
* new manual page EVP_PKCS82PKEY(3), also documenting EVP_PKEY2PKCS8(3)schwarze2021-10-251-1/+2
|
* new manual page PKCS8_pkey_set0(3)schwarze2021-10-251-1/+2
| | | | documenting four PKCS#8 PrivateKeyInfo accessors
* new manual page EVP_PKEY_add1_attr(3) documenting nine functionsschwarze2021-10-221-1/+2
| | | | for associating X.501 Attributes with private keys
* new manual page X509at_add1_attr(3)schwarze2021-10-221-3/+4
| | | | describing five functions to change arrays of X.501 Attribute objects
* new manual page X509at_get_attr(3)schwarze2021-10-221-1/+2
| | | | documenting five X.501 Attribute read accessors
* new manual page X509_ATTRIBUTE_set1_object(3)schwarze2021-10-211-1/+2
| | | | documenting five X.501 Attribute write accessors
* new manual page ASN1_mbstring_copy(3)schwarze2021-10-201-1/+2
| | | | also documenting ASN1_mbstring_ncopy(3)
* new manual page X509_ATTRIBUTE_get0_object(3)schwarze2021-10-201-1/+2
| | | | documenting the four X.501 Attribute read accessors
* document X509_get_pubkey_parameters(3) in a new manual pageschwarze2021-10-191-1/+2
|
* install X509_PKEY_new(3)schwarze2021-10-191-1/+2
|
* split seven functions out of the page X509_VERIFY_PARAM_set_flags(3), whichschwarze2021-10-181-1/+2
| | | | | is becoming excessively long, into a new page X509_VERIFY_PARAM_new(3); no content change
* link X509_STORE_get_by_subject(3) and X509_ocspid_print(3) to the build,schwarze2021-08-061-1/+3
| | | | forgotten in earlier commits
* document X509_LOOKUP_mem(3) in X509_LOOKUP_hash_dir(3)schwarze2021-07-311-1/+2
| | | | and add a new manual page X509_LOOKUP_new(3)
* new manual page X509_policy_check(3)schwarze2021-07-271-1/+2
|
* new manual page X509_policy_tree_level_count(3)schwarze2021-07-261-1/+2
| | | | 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-1/+3
| | | | | 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-1/+2
| | | | related to X509_PURPOSE objects, purpose identifiers, and purpose indices
* Split the functions operating on the X509_VERIFY_PARAM object outschwarze2021-07-221-1/+2
| | | | | | | | | of X509_STORE_CTX_new(3) because i'm about to document five additional functions of this kind and the page X509_STORE_CTX_new(3) is growing unwieldy. No text change yet, except that i added an introductory sentence to the beginning of the DESCRIPTION of the new page.
* Split X509_NAME_hash(3) out of d2i_X509_NAME(3) and documentschwarze2021-07-201-1/+2
| | | | | | | | | | 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.
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2026-02-09 02:07:34 +0000