| Commit message (Collapse) | Author | Age | Files | Lines | ||
|---|---|---|---|---|---|---|
| ... | ||||||
| * | fix a gratuitiously different argument name | schwarze | 2021-10-22 | 1 | -3/+3 | |
| | | ||||||
| * | new manual page X509at_get_attr(3) | schwarze | 2021-10-22 | 3 | -4/+163 | |
| | | | | | documenting five X.501 Attribute read accessors | |||||
| * | Simplify the description of RETURN VALUES. | schwarze | 2021-10-21 | 1 | -10/+4 | |
| | | | | | | | After tb@'s commit x509/x509_lu.c rev. 1.33, it is no longer necessary to talk about X509_LU_* constants as return values from these functions. Feedback and OK from tb@. | |||||
| * | new manual page X509_ATTRIBUTE_set1_object(3) | schwarze | 2021-10-21 | 4 | -6/+276 | |
| | | | | | documenting five X.501 Attribute write accessors | |||||
| * | document ASN1_STRING_set_by_NID(3) | schwarze | 2021-10-20 | 2 | -5/+129 | |
| | | | | | and the three functions related to the global mask | |||||
| * | new manual page ASN1_mbstring_copy(3) | schwarze | 2021-10-20 | 4 | -5/+182 | |
| | | | | | also documenting ASN1_mbstring_ncopy(3) | |||||
| * | new manual page X509_ATTRIBUTE_get0_object(3) | schwarze | 2021-10-20 | 3 | -2/+139 | |
| | | | | | documenting the four X.501 Attribute read accessors | |||||
| * | document X509_ATTRIBUTE_create(3) and X509_ATTRIBUTE_dup(3) | schwarze | 2021-10-20 | 1 | -6/+60 | |
| | | ||||||
| * | document X509_get_pubkey_parameters(3) in a new manual page | schwarze | 2021-10-19 | 5 | -7/+114 | |
| | | ||||||
| * | more precision, fewer words | schwarze | 2021-10-19 | 1 | -28/+43 | |
| | | ||||||
| * | document i2d_PrivateKey_bio(3) and i2d_PrivateKey_fp(3) | schwarze | 2021-10-19 | 1 | -12/+37 | |
| | | ||||||
| * | install X509_PKEY_new(3) | schwarze | 2021-10-19 | 1 | -1/+2 | |
| | | ||||||
| * | document X509_PKEY_new(3) and X509_PKEY_free(3) | schwarze | 2021-10-19 | 4 | -8/+103 | |
| | | ||||||
| * | document X509_VERIFY_PARAM_inherit(3) and X509_VERIFY_PARAM_set1(3) | schwarze | 2021-10-18 | 4 | -8/+159 | |
| | | ||||||
| * | split seven functions out of the page X509_VERIFY_PARAM_set_flags(3), which | schwarze | 2021-10-18 | 5 | -134/+175 | |
| | | | | | | is becoming excessively long, into a new page X509_VERIFY_PARAM_new(3); no content change | |||||
| * | Use unsigned char instead of u_char for two prototypes (like everywhere | tb | 2021-10-14 | 1 | -4/+4 | |
| | | | | | else in libcrypto's manuals and headers). | |||||
| * | As suggested by tb@, merge the description of OPENSSL_EC_NAMED_CURVE | schwarze | 2021-09-14 | 1 | -9/+15 | |
| | | | | | | | | | | | | | | | and OPENSSL_EC_EXPLICIT_CURVE from OpenSSL commit 146ca72c Feb 19 14:35:43 2015 +0000 after tb@ changed the default from 0 to OPENSSL_EC_NAMED_CURVE in ec/ec_lib.c rev. 1.41, which is the same default that OpenSSL uses since 1.1.0. While merging, drop the description of the pre-1.1.0 behaviour. It seems irrelevant to me because tb@ found no application in Debian codesearch using OPENSSL_EC_EXPLICIT_CURVE. A former devious default that was probably never relied upon by anyone does not need to be documented. | |||||
| * | Merge documentation of EC_GROUP_order_bits(3) from the OpenSSL 1.1.1 | schwarze | 2021-09-11 | 1 | -26/+70 | |
| | | | | | | | | | | branch, which is still under a free license. While here, also merge a few other improvements, mostly regarding EC_GROUP_get_order(3) and EC_GROUP_get_cofactor(3); in particular, some statements below RETURN VALUES were outright wrong. This patch includes a few minor tweaks and an addition to HISTORY by me. Feedback and OK tb@. | |||||
| * | Merge documentation for BN_bn2binpad(3), BN_bn2lebinpad(3), | schwarze | 2021-09-11 | 1 | -13/+77 | |
| | | | | | | | | and BN_lebin2bn(3) from the OpenSSL 1.1.1 branch, which is still under a free license. While here, tweak a number of details for clarity. OK tb@ | |||||
| * | Calling OpenSSL_add_all_digests() is no longer needed since the library | millert | 2021-09-10 | 1 | -7/+2 | |
| | | | | | automatically initializes itself. OK tb@ | |||||
| * | Use BN_RAND_* instead of mysterious values in the documentation of | tb | 2021-09-10 | 1 | -7/+19 | |
| | | | | | | | | | BN_rand_range() From OpenSSL 1.1.1l ok beck jsing | |||||
| * | link X509_STORE_get_by_subject(3) and X509_ocspid_print(3) to the build, | schwarze | 2021-08-06 | 1 | -1/+3 | |
| | | | | | forgotten in earlier commits | |||||
| * | new manual page X509_ocspid_print(3) | schwarze | 2021-08-06 | 3 | -6/+66 | |
| | | | | | using input from tb@, and OK tb@ on an earlier version | |||||
| * | add a roff(7) comment marking the API function X509_get_default_private_dir() | schwarze | 2021-08-06 | 1 | -2/+5 | |
| | | | | | | as intentionally undocumented because it is trivial and unused in the wild; OK tb@ | |||||
| * | Document X509_get_default_cert_dir_env(3) | schwarze | 2021-08-03 | 1 | -8/+35 | |
| | | | | | | | | | | and X509_get_default_cert_file_env(3). LibreSSL itself does not call getenv(3), but a few application programs including epic5, fetchmail, fossil, slic3r call these functions, so in case programmers find them in existing code, telling them what they do seems useful. | |||||
| * | Document X509_get_default_cert_area(3). | schwarze | 2021-08-03 | 1 | -7/+41 | |
| | | | | | | | | Put it into this page because this is the code actually using it. Despite its name and include file, it is unrelated to X.509 and unrelated to certificates: it is just the default directory containing the library configuration file, openssl.cnf(5). | |||||
| * | tweaks regarding X509_LOOKUP_by_subject(3): | schwarze | 2021-08-02 | 1 | -8/+28 | |
| | | | | | | | * document the X509_OBJECT output parameter * more precision regarding return values * clarify relationship with X509_LOOKUP_ctrl(3) for the dir lookup method | |||||
| * | new manual page X509_STORE_get_by_subject(3) | schwarze | 2021-08-02 | 5 | -12/+212 | |
| | | ||||||
| * | document X509_STORE_load_mem(3) and X509_STORE_add_lookup(3) | schwarze | 2021-08-01 | 1 | -7/+67 | |
| | | ||||||
| * | document X509_LOOKUP_mem(3) in X509_LOOKUP_hash_dir(3) | schwarze | 2021-07-31 | 8 | -32/+636 | |
| | | | | | and add a new manual page X509_LOOKUP_new(3) | |||||
| * | Move the explanations related to *ptree closer together and correct | schwarze | 2021-07-30 | 1 | -16/+19 | |
| | | | | | | | | | | the lie that *ptree is set upon success - in some cases of success, it is set to NULL, whereas in some cases of failure, a non-trivial tree may be returned. beck@ pointed out that statements related to *ptree were scattered all over the place, and this patch works for him. | |||||
| * | Fix a documentation bug i introduced that tb@ pointed out: | schwarze | 2021-07-29 | 1 | -12/+3 | |
| | | | | | | X509_policy_check(3) never returns 2. If validation succeeds, it always returns 1. | |||||
| * | Document X509_STORE_set_verify_func(3), mostly using text from the | schwarze | 2021-07-29 | 1 | -8/+32 | |
| | | | | | | | | OpenSSL 1.1.1 branch, which is still under a free license, tweaked by me. While here, garbage collect the weird BUGS section. | |||||
| * | document X509_STORE_CTX_get0_parent_ctx(3) | schwarze | 2021-07-29 | 1 | -4/+34 | |
| | | ||||||
| * | document X509_STORE_CTX_set_app_data(3) and X509_STORE_CTX_get_app_data(3) | schwarze | 2021-07-29 | 1 | -4/+51 | |
| | | ||||||
| * | document X509_STORE_CTX_get0_policy_tree(3) | schwarze | 2021-07-28 | 1 | -4/+41 | |
| | | | | | and X509_STORE_CTX_get_explicit_policy(3) | |||||
| * | document X509_policy_tree_free(3) | schwarze | 2021-07-28 | 1 | -3/+19 | |
| | | ||||||
| * | consisely explain the meaning of return values rather than merely | schwarze | 2021-07-28 | 1 | -3/+20 | |
| | | | | | refering to child object names defined in the standard | |||||
| * | Explain the meaning of the policy_oids input argument, correct the | schwarze | 2021-07-28 | 1 | -14/+12 | |
| | | | | | | | description of the *pexplicit_policy output argument and make it less technical, and drop the mention of the expected_policy_set because the library provides no accessor function for it. | |||||
| * | explicitely -> explicitly; | jmc | 2021-07-28 | 1 | -4/+4 | |
| | | ||||||
| * | new manual page X509_policy_check(3) | schwarze | 2021-07-27 | 6 | -10/+198 | |
| | | ||||||
| * | new manual page X509_policy_tree_level_count(3) | schwarze | 2021-07-26 | 4 | -6/+168 | |
| | | | | | documenting the X509_POLICY_TREE object and its sub-objects | |||||
| * | Document X509_STORE_CTX_set_trust(3), X509_STORE_CTX_set_purpose(3), | schwarze | 2021-07-25 | 1 | -4/+226 | |
| | | | | | | and X509_STORE_CTX_purpose_inherit(3). These functions look deceptively simple on first sight, but their semantics is surprisingly complicated. | |||||
| * | Two new manual pages X509_TRUST_set(3) and X509_check_trust(3) | schwarze | 2021-07-24 | 8 | -12/+516 | |
| | | | | | | documenting ten functions related to X509_TRUST objects, trust identifiers, and trust indices. | |||||
| * | Add a roff(7) comment that X509_issuer_and_serial_hash() is | schwarze | 2021-07-23 | 1 | -2/+4 | |
| | | | | | | | intentionally undocumented because it uses MD5 only and is unused in real-world code according to codesearch.debian.net. No objection from tb@. | |||||
| * | clarify the meaning of the argument of X509_VERIFY_PARAM_set_purpose(3) | schwarze | 2021-07-23 | 1 | -10/+16 | |
| | | ||||||
| * | mention the possibility that user-defined purpose identifiers may have | schwarze | 2021-07-23 | 1 | -2/+13 | |
| | | | | | been defined or user-supplied checking functions may have been installed | |||||
| * | new manual page X509_PURPOSE_set(3) documenting 11 functions | schwarze | 2021-07-23 | 4 | -5/+303 | |
| | | | | | related to X509_PURPOSE objects, purpose identifiers, and purpose indices | |||||
| * | occured -> occurred; | jmc | 2021-07-23 | 1 | -3/+3 | |
| | | ||||||
| * | document X509_STORE_CTX_set_time(3) and X509_STORE_CTX_set_depth(3) | schwarze | 2021-07-22 | 1 | -2/+34 | |
| | | ||||||
 |
index : openbsd | |
| A mirror of https://github.com/libressl/openbsd.git |
| summaryrefslogtreecommitdiff |