summaryrefslogtreecommitdiff
path: root/src/lib/libc/stdlib/reallocarray.c (unfollow)
Commit message (Collapse)AuthorFilesLines
2021-08-18Refactor the legacy chain validation from the chain adding code into itsbeck1-52/+70
own function, in preparation for subesquent change. No functional change. ok tb@
2021-08-16typo in commenttb1-2/+2
2021-08-11add new (unsupported) eddsa in certificate verify teststb1-1/+3
2021-08-06link X509_STORE_get_by_subject(3) and X509_ocspid_print(3) to the build,schwarze1-1/+3
forgotten in earlier commits
2021-08-06new manual page X509_ocspid_print(3)schwarze3-6/+66
using input from tb@, and OK tb@ on an earlier version
2021-08-06add a roff(7) comment marking the API function X509_get_default_private_dir()schwarze1-2/+5
as intentionally undocumented because it is trivial and unused in the wild; OK tb@
2021-08-04SSL_CTX_remove_session() checks for a NULL session, avoid doing it twice.jsing1-2/+2
Noted by tb@ during review of a larger change.
2021-08-03Document X509_get_default_cert_dir_env(3)schwarze1-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.
2021-08-03Document X509_get_default_cert_area(3).schwarze1-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).
2021-08-02tweaks regarding X509_LOOKUP_by_subject(3):schwarze1-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
2021-08-02new manual page X509_STORE_get_by_subject(3)schwarze5-12/+212
2021-08-01document X509_STORE_load_mem(3) and X509_STORE_add_lookup(3)schwarze1-7/+67
2021-07-31document X509_LOOKUP_mem(3) in X509_LOOKUP_hash_dir(3)schwarze8-32/+636
and add a new manual page X509_LOOKUP_new(3)
2021-07-31We have defines for alert levels - use them instead of magic numbers.jsing2-7/+5
2021-07-30Move the explanations related to *ptree closer together and correctschwarze1-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.
2021-07-29Ensure that the kill signal undergoing testing is not ignored.anton1-1/+15
ok bluhm@
2021-07-29Fix a documentation bug i introduced that tb@ pointed out:schwarze1-12/+3
X509_policy_check(3) never returns 2. If validation succeeds, it always returns 1.
2021-07-29Document X509_STORE_set_verify_func(3), mostly using text from theschwarze1-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.
2021-07-29document X509_STORE_CTX_get0_parent_ctx(3)schwarze1-4/+34
2021-07-29document X509_STORE_CTX_set_app_data(3) and X509_STORE_CTX_get_app_data(3)schwarze1-4/+51
2021-07-28document X509_STORE_CTX_get0_policy_tree(3)schwarze1-4/+41
and X509_STORE_CTX_get_explicit_policy(3)
2021-07-28document X509_policy_tree_free(3)schwarze1-3/+19
2021-07-28consisely explain the meaning of return values rather than merelyschwarze1-3/+20
refering to child object names defined in the standard
2021-07-28Explain the meaning of the policy_oids input argument, correct theschwarze1-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.
2021-07-28explicitely -> explicitly;jmc1-4/+4
2021-07-27new manual page X509_policy_check(3)schwarze6-10/+198
2021-07-26Add error checks for i2d_X509_NAME()tb1-3/+5
This avoids potential malloc(-1) and malloc(0), spotted by schwarze while documenting X509_ocspid_print(). ok schwarze
2021-07-26new manual page X509_policy_tree_level_count(3)schwarze4-6/+168
documenting the X509_POLICY_TREE object and its sub-objects
2021-07-26Dedup dtls1_dispatch_alert()/ssl3_dispatch_alert().jsing6-65/+26
The code for dtls1_dispatch_alert() and ssl3_dispatch_alert() is largely identical - with a bit of reshuffling we can use ssl3_dispatch_alert() for both protocols and remove the ssl_dispatch_alert function pointer. ok inoguchi@ tb@
2021-07-25Document X509_STORE_CTX_set_trust(3), X509_STORE_CTX_set_purpose(3),schwarze1-4/+226
and X509_STORE_CTX_purpose_inherit(3). These functions look deceptively simple on first sight, but their semantics is surprisingly complicated.
2021-07-24Two new manual pages X509_TRUST_set(3) and X509_check_trust(3)schwarze8-12/+516
documenting ten functions related to X509_TRUST objects, trust identifiers, and trust indices.
2021-07-24Compare strcmp and strcasecmp return value with zeroinoguchi1-6/+6
2021-07-24Add basic regression tests for strchr() and strrchr().visa3-2/+79
2021-07-23Similar to x509/x509_purp.c rev. 1.5:schwarze1-5/+1
Delete some code from X509_TRUST_cleanup(3) that had no effect: it called a function on static objects that returns right away unless the argument is dynamically allocated. Pointed out by tb@. This commit is identical to: OpenSSL commit 5e6e650d62af09f47d63bfdd6c92e3b16e9da644 Author: Kurt Cancemi <kurt at x64architecture dot com> Date: Thu Jun 9 21:57:36 2016 -0400
2021-07-23Delete some code from X509_PURPOSE_cleanup(3) that had no effect:schwarze1-5/+1
it called a function on static objects that returns right away unless the argument is dynamically allocated. OK jsing@ tb@ The useless code was independently discovered while writing documentation. This commit is identical to: OpenSSL commit fa3a0286d178eb3b87bf2eb5fd7af40f81453314 Author: Kurt Cancemi <kurt at x64architecture dot com> Date: Wed Jun 8 19:15:38 2016 -0400
2021-07-23Add a roff(7) comment that X509_issuer_and_serial_hash() isschwarze1-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@.
2021-07-23Make MALLOC_STATS compile again; noted by Omar Polo and Joe Nelsonotto1-2/+2
2021-07-23clarify the meaning of the argument of X509_VERIFY_PARAM_set_purpose(3)schwarze1-10/+16
2021-07-23mention the possibility that user-defined purpose identifiers may haveschwarze1-2/+13
been defined or user-supplied checking functions may have been installed
2021-07-23new manual page X509_PURPOSE_set(3) documenting 11 functionsschwarze4-5/+303
related to X509_PURPOSE objects, purpose identifiers, and purpose indices
2021-07-23occured -> occurred;jmc1-3/+3
2021-07-22document X509_STORE_CTX_set_time(3) and X509_STORE_CTX_set_depth(3)schwarze1-2/+34
2021-07-22Major cleanup.schwarze1-85/+66
1. Fix the order of functions to match the order they occur in application code, making the text significantly easier to follow. 2. Do not use the same argument placeholder *sk for several different things; call the arguments *trusted, *untrusted, and *crls as appropriate. 3. Avoid using the word "initialised" for two different concepts in the same manual page; it was sometimes intended to mean "fill with zeros" and sometimes "replace the zeros with useful data". 4. Generally, make the text more precise, more straightforward, and shorter (-84 +65 lines of mdoc code).
2021-07-22Split the functions operating on the X509_VERIFY_PARAM object outschwarze3-74/+172
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.
2021-07-22document X509_STORE_CTX_get0_current_issuer(3)schwarze1-5/+51
and X509_STORE_CTX_get0_current_crl(3)
2021-07-22Move X509_STORE_CTX_get0_cert(3) to the X509_STORE_CTX_new(3) manual.schwarze2-65/+113
OpenSSL documents it in X509_STORE_CTX_get_error(3), but it is misplaced there. It has nothing to do with accessing status or error information but merely retrieves a pointer to the certificate that the users wants to validate. It is a companion function to X509_STORE_CTX_init(3), X509_STORE_CTX_set_cert(3), X509_STORE_CTX_get0_store(3), and X509_STORE_CTX_get0_untrusted(3). While here: 1. Clarify how the new, init, verify, cleanup, and free calls interact, and who owns the memory involved, because this is all really confusing from the user perspective. 2. Clarify how X509_STORE_CTX_init(3), X509_STORE_CTX_set_cert(3), and X509_STORE_CTX_set_chain(3) partially override each other. 3. Move X509_STORE_CTX_set0_untrusted(3) to the proper place because it is the same as X509_STORE_CTX_set_chain(3). 4. Add a few missing words and improve some wordings.
2021-07-21Document X509_STORE_CTX_get_chain(3).schwarze1-5/+15
It is deprecated, but it is still called by various application programs, so let's better mention it.
2021-07-21Remove DTLS processed_rcds queue.jsing3-50/+22
When DTLS handshake records are received from the next epoch, we will potentially queue them on the unprocessed_rcds queue - this is usually a Finished message that has been received without the ChangeCipherSuite (CCS) message (which may have been dropped or reordered). After the epoch increments (due to the CCS being received), the current code processes all records on the unprocessed queue and immediate queues them on the processed queue, which dtls1_get_record() then pulls from. This form of processing only adds more complexity and another queue. Instead, once the epoch increments, pull a single record from the unprocessed queue and process it, allowing the contents to be consumed by the caller. We repeat this process until the unprocessed queue is empty, at which point we go back to consuming messages from the wire. ok inoguchi@ tb@
2021-07-21Silently discard invalid DTLS records.jsing1-4/+11
Per RFC 6347 section 4.1.2.1, DTLS should silently discard invalid records, including those that have a bad MAC. When converting to the new record layer, we inadvertantly switched to standard TLS behaviour, where an invalid record is fatal. This restores the previous behaviour. Issue noted by inoguchi@ ok inoguchi@
2021-07-20Split X509_NAME_hash(3) out of d2i_X509_NAME(3) and documentschwarze4-25/+102
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 2025-05-25 04:19:39 +0000