summaryrefslogtreecommitdiff
path: root/src/lib/libc/stdlib/recallocarray.c (unfollow)
Commit message (Collapse)AuthorFilesLines
2018-02-15Add missing RETURN VALUES section;schwarze1-3/+11
from Paul Yang via OpenSSL commit 1f13ad31 Dec 25 17:50:39 2017 +0800.
2018-02-15Document the additional public function OCSP_basic_sign(3);schwarze1-5/+42
from David Cooper <david.cooper@nist.gov> via OpenSSL commit cace14b8 Jan 24 11:47:23 2018 -0500.
2018-02-15Import the new manual page EVP_PKEY_meth_new(3) from OpenSSL,schwarze13-20/+557
removing parts that don't apply to OpenBSD.
2018-02-15In some EXAMPLES, correct calls to EVP_PKEY_CTX_new(3) thatschwarze5-35/+51
lacked an argument; from Jakub Jelen <jjelen at redhat dot com> via OpenSSL commit 9db6673a Jan 17 19:23:37 2018 -0500.
2018-02-15Import the new manual page EVP_PKEY_asn1_get_count(3) from OpenSSL,schwarze2-1/+161
fixing half a dozen bugs and typos and also tweaking the wording a bit.
2018-02-15In x509_vfy.h rev. 1.20 2018/02/14 17:06:34, jsing@ providedschwarze2-19/+57
X509_STORE_CTX_set0_untrusted(3), X509_STORE_CTX_set0_trusted_stack(3), X509_STORE_CTX_get0_untrusted(3), and X509_STORE_CTX_get0_cert(3). Merge the related documentation from OpenSSL.
2018-02-15In x509.h rev. 1.28 2018/02/14 16:57:25, jsing@schwarze2-1/+76
provided X509_get0_notBefore(3) and its three friends. Write a manual page from scratch because what OpenSSL has is confusing and incomplete. By the way, providing two identical functions differing only in the constness of the returned structure is crazy. Are application programmers expected to be too stupid to write const ASN1_TIME *notBefore = X509_getm_notBefore(x) if that's what they want?
2018-02-15Fix typo: s/Vt strict tm/Vt struct tm/schwarze1-3/+3
2018-02-15In asn1.h rev. 1.44 2018/02/14 16:46:04, jsing@schwarze1-8/+25
provided ASN1_STRING_get0_data(3). Merge the corresponding documentation from OpenSSL.
2018-02-14In evp.h rev. 1.54 2018/02/14 16:40:42, jsing@ provided EVP_PKEY_up_ref(3).schwarze1-4/+22
Merge the documentation from OpenSSL commits 0c497e96 Dec 14 18:10:16 2015 +0000 and c5ebfcab Mar 7 22:45:58 2016 +0100 with tweaks by me.
2018-02-14In x509.h rev. 1.27 2018/02/14 16:18:10, jsing@ providedschwarze2-1/+80
X509_get_signature_nid(3). Add a new manual page for it based on the relevant parts of OpenSSL X509_get0_signature.pod.
2018-02-14In ssl.h rev. 1.136 2018/02/14 17:08:44, jsing@ providedschwarze1-15/+32
SSL_CTX_up_ref(3). Merge the related documentation from OpenSSL, but tweak the wording to be less confusing and simplify the RETURN VALUES section.
2018-02-14In ssl.h rev. 1.135 2018/02/14 16:16:10, jsing@ providedschwarze1-4/+42
SSL_CTX_get0_param(3) and SSL_get0_param(3). Merge the related documentation from OpenSSL, with small tweaks.
2018-02-14Bump lib{crypto,ssl,tls} minors due to symbol additions.jsing3-3/+3
2018-02-14Provide SSL_CTX_up_ref().jsing3-2/+11
2018-02-14Provide X509_STORE_CTX_get0_{cert,untrusted}() andjsing3-3/+35
X509_STORE_CTX_set0_{trusted_stack,untrusted}().
2018-02-14Provide X509_get{0,m}_not{Before,After}().jsing3-5/+41
2018-02-14Provide ASN1_STRING_get0_data().jsing3-3/+11
2018-02-14Provide EVP_PKEY_up_ref().jsing3-2/+11
2018-02-14Start providing parts of the OpenSSL 1.1 API.jsing3-2/+24
This will ease the burden on ports and others trying to make software work with LibreSSL, while avoiding #ifdef mazes. Note that we are not removing 1.0.1 API or making things opaque, hence software written to use the older APIs will continue to work, as will software written to use the 1.1 API (as more functionality become available). Discussed at length with deraadt@ and others.
2018-02-14Provide X509_get_signature_nid().jsing3-12/+21
2018-02-14Provide SSL_CTX_get0_param() and SSL_get0_param().jsing3-5/+20
Some applications that use X509_VERIFY_PARAM expect these to exist, since they're also part of the OpenSSL 1.0.2 API.
2018-02-14Update keypair regress to match revised keypair hash handling.jsing1-11/+10
Apparently I failed to commit this when I committed the libtls change...
2018-02-14New manual page EVP_PKEY_asn1_new(3) from Richard Levitteschwarze8-13/+475
via OpenSSL commit 751148e2 Oct 27 00:11:11 2017 +0200, including only the parts related to functions that exist in OpenBSD. The design of these interfaces is not particularly pretty, they are not particularly easy to document, and the manual page does not look particularly good when formatted, but what can we do, things are as they are...
2018-02-14I recently documented X509_VERIFY_PARAM_lookup(3), so change .Fn to .Xr.schwarze1-3/+3
2018-02-14Mention two more block cipher modes that actually exist in our tree;schwarze1-8/+30
from Patrick dot Steuer at de dot ibm dot com via OpenSSL commit 338ead0f Oct 9 12:16:34 2017 +0200. Correct the EVP_EncryptUpdate(3) and EVP_DecryptUpdate(3) prototypes; from FdaSilvaYY at gmail dot com via OpenSSL commit 7bbb0050 Nov 22 22:00:29 2017 +0100. Document the additional public function EVP_CIPHER_CTX_rand_key(3); from Patrick dot Steuer at de dot ibm dot com via OpenSSL commit 5c5eb286 Dec 5 00:36:43 2017 +0100.
2018-02-13Add the missing RETURN VALUES section.schwarze1-5/+118
Mostly from Paul Yang via OpenSSL commit 1f13ad31 Dec 25 17:50:39 2017 +0800, tweaked by me for conciseness and accuracy.
2018-02-13Add the missing RETURN VALUES section, mostly from Paul Yangschwarze1-11/+38
via OpenSSL commit 1f13ad31 Dec 25 17:50:39 2017 +0800, but fixing two bugs in his description. This commit also includes a few minor improvements to the description of DES_fcrypt(3), also from OpenSSL, tweaked by me.
2018-02-13Correctly describe BN_get_word(3) and BN_set_word(3).schwarze1-20/+25
These functions constitute an obvious portability nightmare, but that's no excuse for incorrect documentation. Pointed out by Nicolas Schodet via OpenSSL commit b713c4ff Jan 22 14:41:09 2018 -0500.
2018-02-13Mention that BN_new(3) sets the value to zero;schwarze1-5/+6
from Hubert Kario <hkario at redhat dot com> via OpenSSL commit 681acb31 Sep 29 13:10:34 2017 +0200.
2018-02-13Delete duplicate .Nm entry in the NAME section,schwarze1-4/+4
from Rich Salz via OpenSSL commit 8162f6f5 Jun 9 17:02:59 2016 -0400. Merging the RETURN VALUES section really wouldn't make much sense here, it contains no additional information and i don't see any way to reorganize the content and make it better.
2018-02-13Add the missing RETURN VALUES section.schwarze1-14/+76
Triggered by OpenSSL commit 1f13ad31 Dec 25 17:50:39 2017 +0800 by Paul Yang, but reworded for intelligibility and precision. While here, also expand the description of the "ret" argument of BIO_callback_fn(). That's a fairly complicated and alarmingly powerful concept, but the description was so brief that is was barely comprehensible.
2018-02-12Add the missing RETURN VALUES section;schwarze1-3/+21
from Paul Yang via OpenSSL commit 1f13ad31 Dec 25 17:50:39 2017 +0800 with tweaks by me.
2018-02-12Add the missing RETURN VALUES section;schwarze1-3/+15
from Paul Yang via OpenSSL commit 1f13ad31 Dec 25 17:50:39 2017 +0800.
2018-02-12Add missing RETURN VALUES section.schwarze1-4/+15
From Paul Yang via OpenSSL commit 1f13ad31 Dec 25 17:50:39 2017 +0800 with one tweak.
2018-02-12Add the missing RETURN VALUES section and reorder the contentschwarze1-35/+93
accordingly. Make some statements more precise, and point out some dangerous traps in these ill-designed interfaces. Also do some minor polishing while here. Triggered by OpenSSL commit 1f13ad31 Dec 25 17:50:39 2017 +0800 by Paul Yang, but not using most of his wording because that is in part redundant, in part incomplete, and in part outright wrong.
2018-02-11Document three more functions recently made public by jsing@schwarze1-18/+185
as requested by jsing@, and also document six more related functions that have already been public before that. OpenSSL fails to document any of these.
2018-02-11typo in output string; from edgar pettijohnjmc1-2/+2
2018-02-11Merge documentation from OpenSSL for seven functionsschwarze1-7/+196
that jsing@ recently exposed publicly in libcrypto. Requested by jsing@.
2018-02-10Be more specific about when the session file will be updated.jsing1-2/+2
2018-02-10Bump TLS API version since we've added more functionality.jsing1-2/+2
2018-02-10Move the keypair pubkey hash handling code to during config.jsing4-69/+95
The keypair pubkey hash was being generated and set in the keypair when the TLS context was being configured. This code should not be messing around with the keypair contents, since it is part of the config (and not the context). Instead, generate the pubkey hash and store it in the keypair when the certificate is configured. This means that we are guaranteed to have the pubkey hash and as a side benefit, we identify bad certificate content when it is provided, instead of during the context configuration. ok beck@
2018-02-10Tidy/standardise some code.jsing1-6/+3
2018-02-10Remove NULL check from tls_conninfo_cert_pem() - all of the other conninfojsing1-3/+1
functions require the conninfo passed in to be non-NULL.
2018-02-10Document functions for client-side TLS session support.jsing2-9/+56
2018-02-10Add support to libtls for client-side TLS session resumption.jsing6-5/+195
A libtls client can specify a session file descriptor (a regular file with appropriate ownership and permissions) and libtls will manage reading and writing of session data across TLS handshakes. Discussed at length with deraadt@ and tedu@. Rides previous minor bump. ok beck@
2018-02-10Bump lib{crypto,ssl,tls} minors due to symbol addition.jsing3-3/+3
2018-02-10Expose X509_VERIFY_PARAM_* functions that appeared in the OpenSSL 1.0.2jsing2-1/+26
API and are now in use by various libraries and applications.
2018-02-08Update regress to use tlsext_serverhello_parse().jsing1-5/+3
2018-02-08Complete the TLS extension rewrite on the client-side.jsing4-156/+93
The RI logic gets pulled up into ssl3_get_server_hello() and ssl_parse_serverhello_tlsext() gets replaced by tlsext_client_parse(), which allows a CBS to be passed all the way down. This also deduplicates the tlsext_client_build() and tlsext_server_build() code. ok beck@
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-08-20 03:32:54 +0000