summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* Fix behaviour of OpenSSL_version().jsing2018-02-171-2/+16
| | | | | | | The constant values do not map 1:1 to SSLeay_version(), so implement it separately. Issue noted by schwarze@
* typo fix s/issuserAltName/issuerAltName/schwarze2018-02-161-4/+6
| | | | | from Andrew Siplas <andrew at asiplas dot net> via OpenSSL commit 36cf10cf Oct 4 02:11:08 2017 -0400
* Copy all function names from the SYNOPSIS to the NAME section becauseschwarze2018-02-161-6/+108
| | | | | | i found another page containing an .Xr to one of the functions that were not in the NAME section. This manual page is ugly either way; just ugly is better than broken links in addition to ugly.
* Merge OpenSSL commit a8c5ed81 Jul 18 13:57:25 2017 -0400schwarze2018-02-161-4/+8
| | | | | | | | | from <xemdetia at 808inorganic dot com>. Original commit message: "Document default section and library configuration. It is talked around but not explicitly stated in one part of the documentation that you should put library configuration lines at the start of the configuration file."
* Add missing RETURN VALUES sections; from Paul Yangschwarze2018-02-162-8/+36
| | | | via OpenSSL commit 1f13ad31 Dec 25 17:50:39 2017 +0800 tweaked by me.
* Add missing RETURN VALUES sections; from Paul Yangschwarze2018-02-163-15/+78
| | | | via OpenSSL commit 1f13ad31 Dec 25 17:50:39 2017 +0800, tweaked by me.
* Merge the new RETURN VALUES section from Paul Yang,schwarze2018-02-151-7/+78
| | | | | | OpenSSL commit 1f13ad31 Dec 25 17:50:39 2017 +0800, with a number of fixes by me. Also include three earlier, minor improvements from OpenSSL.
* Add missing RETURN VALUES section; from Paul Yangschwarze2018-02-151-3/+9
| | | | via OpenSSL commit 1f13ad31 Dec 25 17:50:39 2017 +0800.
* Fix the STANDARDS section, but in a different way than in OpenSSLschwarze2018-02-151-4/+8
| | | | | | | because i see no indication that a 2016 revision of this standard might exist. Instead, use information from: https://www.iso.org/standard/39876.html and https://www.iso.org/standard/60475.html
* Quite absurdly, the OpenSSL folks have been actively mucking aroundschwarze2018-02-151-3/+9
| | | | | | | | with their random subsystem in 2017 rather than relying on the operating system, which made me check the changes to their manual pages, which caused me to notice that they document another public function as non-deprecated that we neutered: RAND_poll(3). Mention it briefly.
* Add missing RETURN VALUES section;schwarze2018-02-151-3/+11
| | | | from Paul Yang via OpenSSL commit 1f13ad31 Dec 25 17:50:39 2017 +0800.
* Document the additional public function OCSP_basic_sign(3);schwarze2018-02-151-5/+42
| | | | | from David Cooper <david.cooper@nist.gov> via OpenSSL commit cace14b8 Jan 24 11:47:23 2018 -0500.
* Import the new manual page EVP_PKEY_meth_new(3) from OpenSSL,schwarze2018-02-1513-20/+557
| | | | removing parts that don't apply to OpenBSD.
* In some EXAMPLES, correct calls to EVP_PKEY_CTX_new(3) thatschwarze2018-02-155-35/+51
| | | | | lacked an argument; from Jakub Jelen <jjelen at redhat dot com> via OpenSSL commit 9db6673a Jan 17 19:23:37 2018 -0500.
* Import the new manual page EVP_PKEY_asn1_get_count(3) from OpenSSL,schwarze2018-02-152-1/+161
| | | | fixing half a dozen bugs and typos and also tweaking the wording a bit.
* In x509_vfy.h rev. 1.20 2018/02/14 17:06:34, jsing@ providedschwarze2018-02-152-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.
* In x509.h rev. 1.28 2018/02/14 16:57:25, jsing@schwarze2018-02-152-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?
* Fix typo: s/Vt strict tm/Vt struct tm/schwarze2018-02-151-3/+3
|
* In asn1.h rev. 1.44 2018/02/14 16:46:04, jsing@schwarze2018-02-151-8/+25
| | | | | provided ASN1_STRING_get0_data(3). Merge the corresponding documentation from OpenSSL.
* In evp.h rev. 1.54 2018/02/14 16:40:42, jsing@ provided EVP_PKEY_up_ref(3).schwarze2018-02-141-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.
* In x509.h rev. 1.27 2018/02/14 16:18:10, jsing@ providedschwarze2018-02-142-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.
* Bump lib{crypto,ssl,tls} minors due to symbol additions.jsing2018-02-141-1/+1
|
* Provide X509_STORE_CTX_get0_{cert,untrusted}() andjsing2018-02-143-3/+35
| | | | X509_STORE_CTX_set0_{trusted_stack,untrusted}().
* Provide X509_get{0,m}_not{Before,After}().jsing2018-02-143-5/+41
|
* 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
|
* 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.
* Merge documentation from OpenSSL for seven functionsschwarze2018-02-111-7/+196
| | | | | that jsing@ recently exposed publicly in libcrypto. Requested by jsing@.
* Bump lib{crypto,ssl,tls} minors due to symbol addition.jsing2018-02-101-1/+1
|
* 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.
* Restore the old behavior when a port number without a host name isbluhm2018-02-071-10/+12
| | | | | | passed to BIO_get_accept_socket(). This is part of the API and it fixes "openssl ocsp -port 12345" in server mode. from markus@; OK jsing@ beck@
* Do not call freeaddrinfo() with a NULL parameter.bluhm2018-02-061-2/+3
| | | | OK jsing@
* Make the NEON codepaths conditional on __STRICT_ALIGNMENT not beingkettenis2018-01-243-5/+5
| | | | | | defined as they rely on unaligned access. ok joel@
* On OpenBSD/armv7 we deliberately trap unaligned access. Unfortunatelykettenis2018-01-075-12/+16
| | | | | | | | the assembly code in libcrypto assumes unaligned access is allowed for ARMv7. Make these paths conditional on __STRICT_ALIGNMENT not being defined and define __STRICT_ALIGNMENT in arm_arch.h for OpenBSD. ok tom@
* bump to 2.7.0bcook2017-12-111-3/+3
|
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-03-24 18:24:04 +0000