summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* Provide ASN1_STRING_get0_data().jsing2018-02-143-3/+11
|
* Provide EVP_PKEY_up_ref().jsing2018-02-143-2/+11
|
* Start providing parts of the OpenSSL 1.1 API.jsing2018-02-143-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.
* Provide X509_get_signature_nid().jsing2018-02-143-12/+21
|
* Provide SSL_CTX_get0_param() and SSL_get0_param().jsing2018-02-143-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.
* Update keypair regress to match revised keypair hash handling.jsing2018-02-141-11/+10
| | | | Apparently I failed to commit this when I committed the libtls change...
* New manual page EVP_PKEY_asn1_new(3) from Richard Levitteschwarze2018-02-148-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...
* I recently documented X509_VERIFY_PARAM_lookup(3), so change .Fn to .Xr.schwarze2018-02-141-3/+3
|
* Mention two more block cipher modes that actually exist in our tree;schwarze2018-02-141-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.
* Add the missing RETURN VALUES section.schwarze2018-02-131-5/+118
| | | | | Mostly from Paul Yang via OpenSSL commit 1f13ad31 Dec 25 17:50:39 2017 +0800, tweaked by me for conciseness and accuracy.
* Add the missing RETURN VALUES section, mostly from Paul Yangschwarze2018-02-131-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.
* Correctly describe BN_get_word(3) and BN_set_word(3).schwarze2018-02-131-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.
* Mention that BN_new(3) sets the value to zero;schwarze2018-02-131-5/+6
| | | | | from Hubert Kario <hkario at redhat dot com> via OpenSSL commit 681acb31 Sep 29 13:10:34 2017 +0200.
* Delete duplicate .Nm entry in the NAME section,schwarze2018-02-131-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.
* Add the missing RETURN VALUES section.schwarze2018-02-131-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.
* Add the missing RETURN VALUES section;schwarze2018-02-121-3/+21
| | | | | from Paul Yang via OpenSSL commit 1f13ad31 Dec 25 17:50:39 2017 +0800 with tweaks by me.
* Add the missing RETURN VALUES section;schwarze2018-02-121-3/+15
| | | | from Paul Yang via OpenSSL commit 1f13ad31 Dec 25 17:50:39 2017 +0800.
* Add missing RETURN VALUES section.schwarze2018-02-121-4/+15
| | | | | From Paul Yang via OpenSSL commit 1f13ad31 Dec 25 17:50:39 2017 +0800 with one tweak.
* Add the missing RETURN VALUES section and reorder the contentschwarze2018-02-121-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.
* Document three more functions recently made public by jsing@schwarze2018-02-111-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.
* typo in output string; from edgar pettijohnjmc2018-02-111-2/+2
|
* Merge documentation from OpenSSL for seven functionsschwarze2018-02-111-7/+196
| | | | | that jsing@ recently exposed publicly in libcrypto. Requested by jsing@.
* Be more specific about when the session file will be updated.jsing2018-02-101-2/+2
|
* Bump TLS API version since we've added more functionality.jsing2018-02-101-2/+2
|
* Move the keypair pubkey hash handling code to during config.jsing2018-02-104-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@
* Tidy/standardise some code.jsing2018-02-101-6/+3
|
* Remove NULL check from tls_conninfo_cert_pem() - all of the other conninfojsing2018-02-101-3/+1
| | | | functions require the conninfo passed in to be non-NULL.
* Document functions for client-side TLS session support.jsing2018-02-102-9/+56
|
* Add support to libtls for client-side TLS session resumption.jsing2018-02-106-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@
* Bump lib{crypto,ssl,tls} minors due to symbol addition.jsing2018-02-103-3/+3
|
* Expose X509_VERIFY_PARAM_* functions that appeared in the OpenSSL 1.0.2jsing2018-02-102-1/+26
| | | | API and are now in use by various libraries and applications.
* Update regress to use tlsext_serverhello_parse().jsing2018-02-081-5/+3
|
* Complete the TLS extension rewrite on the client-side.jsing2018-02-084-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@
* Convert option handling for openssl(1) genpkey.jsing2018-02-081-110/+177
| | | | ok beck@ inoguchi@
* Update regress to match change to tls_keypair_pubkey_hash().jsing2018-02-081-3/+4
|
* Have tls_keypair_pubkey_hash() call tls_keypair_load_cert() instead ofjsing2018-02-083-14/+11
| | | | | rolling its own certificate loading. This also means we get better error reporting on failure.
* Add a regress test that covers libtls keypairs.jsing2018-02-083-1/+248
|
* Tweak compiler flags to include -DLIBRESSL_INTERNAL and make more warningsjsing2018-02-081-2/+2
| | | | fatal.
* Ensure that tls_keypair_clear() clears the OCSP staple and pubkey hash.jsing2018-02-081-6/+5
|
* Do not bother NULLing pointers in a struct that is about to be freed.jsing2018-02-081-10/+1
|
* Move tls_keypair_pubkey_hash() to the keypair file.jsing2018-02-083-43/+43
|
* Avoid a memory leak that results when the same tls_config is reused.jsing2018-02-081-1/+4
| | | | Reported by and fix from Nate Bessette <openbsd at nate dot sh> - thanks.
* Assert tedu's copyright since some of the code moved here is his.jsing2018-02-081-1/+2
|
* Split keypair handling out into its own file - it had already appearedjsing2018-02-086-166/+215
| | | | | | in multiple locations. ok beck@
* use consistent style for for loop in unmap(), no functional changeotto2018-02-071-4/+2
|
* Restore a check before BN_free() that needs to exist and write it such thatjsing2018-02-071-2/+3
| | | | the intent is more obvious.
* Nuke some more free NULL guards.jsing2018-02-071-9/+5
|
* Indent labels with a single space so that diff prototypes are more useful.jsing2018-02-0745-190/+190
|
* Add more free functions for NULL checks.jsing2018-02-071-16/+67
|
* Remove guards around *_free() calls since these functions handle NULL.jsing2018-02-0718-114/+67
|
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-03-19 19:59:06 +0000