aboutsummaryrefslogtreecommitdiffstats
path: root/socket.c
Commit message (Collapse)AuthorAgeFilesLines
* Bump wolfSSL requirement to 5.1.1 and get ready for fetchmail 6.4.27.Matthias Andree2022-01-261-2/+2
|
* wolfSSL: work around SSL_peek() error on handshakeMatthias Andree2021-12-261-1/+9
| | | | | | | | | | | | See https://github.com/wolfSSL/wolfssl/issues/4593 The earlier assumption that SSL_CTX_set_mode() worked was untrue (wolfSSL 5.0.0 does not implement it), and masked by the selection of servers used for testing. Also, wolfSSL 5.0.0 does not implement SSL_CTX_set_mode(), which went unnoticed because the interface does not support returning errors (it returns the updated mode bitfield value).
* Realign comments and variable names.Matthias Andree2021-12-051-4/+4
|
* Permit LibreSSL on OpenBSD.Matthias Andree2021-12-051-2/+6
| | | | | | | | On OpenBSD, libressl is "normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs" according to Stuart Henderson, so according to the GNU GPL v2 clause 3, we can permit LibreSSL for OpenBSD.
* socket.c: SSL_peek/SSL_read consistency fixes.Matthias Andree2021-11-281-19/+16
|
* socket.c: SSL_CTX_set_mode(SSL_MODE_AUTO_RETRY)Matthias Andree2021-11-281-1/+3
| | | | | | | | This is the proper fix for wolfSSL 5.0 and OpenSSL before 1.1.1 to avoid the "SSL_peek()" not truly blocking issue. Only OpenSSL 1.1.1 enables this mode by default, so make this explicit.
* Revert "wolfSSL: workaround 5.0.0 SSL_peek() not truly blocking."Matthias Andree2021-11-281-2/+1
| | | | This reverts commit 0d32056e7b14bd029aa375f59230a3ad3e2bae51.
* wolfSSL: support WOLFSSL_TRUST_FILE as default trust storeMatthias Andree2021-11-211-4/+30
| | | | | ...because wolfSSL 5.0.0 does not support a default trust store, unlike OpenSSL.
* wolfSSL: workaround 5.0.0 SSL_peek() not truly blocking.Matthias Andree2021-11-211-1/+2
| | | | | | | | SSL_peek() may return 0 on blocking I/O with SSL_get_error() returning SSL_ERROR_WANT_READ. This should not occur on blocking I/O, and does not occur with OpenSSL 1.0.2, 1.1.1, 3.0. This caused a socket error right after SSL negotiation.
* wolfSSL: support 5.0.0+.Matthias Andree2021-11-211-13/+43
|
* Fix X509_V_FLAG_TRUSTED_FIRST OpenSSL 1.0.2 workaroundMatthias Andree2021-11-201-5/+6
| | | | | | | | The original comparison contained a typo, 0x1000200fL == (ver & 0xfffff000L) and could never match. Fix, and also match at compile time to not even reference this flag on other OpenSSL versions.
* OpenSSL: bump minimum required version to 1.0.2fMatthias Andree2021-11-201-3/+3
| | | | | ...in order to safely remove the obsolete OpenSSL flag SSL_OP_SINGLE_DH_USE.
* LibreSSL: block, due to licensing issue.Matthias Andree2021-11-201-2/+2
| | | | See COPYING or NEWS.
* TLS: OpenSSL 1.0.2 workaround Let's Encrypt ExpiryMatthias Andree2021-11-011-1/+15
| | | | ...of cross-signed certificate.
* socket.c: invalid sslproto no longer abort()sMatthias Andree2021-08-281-2/+0
|
* socket.c: plugin/plugout SIGSEGV and memleak fixesMatthias Andree2021-08-261-12/+26
|
* socket.c: SSL_use_PrivateKey_file <- SSL_use_RSAPrivateKey_file,Matthias Andree2021-03-131-1/+1
| | | | | the latter is deprecated in OpenSSL 3, and the user might use some other key than RSA.
* OpenSSL: permit deprecated features,Matthias Andree2021-03-131-1/+5
| | | | to avoid compatibility issues with new OpenSSL versions later on.
* socket.c clean up code duplication.Matthias Andree2021-02-271-2/+2
|
* --version: print OpenSSL versions build/run-time and directoriesMatthias Andree2021-01-301-8/+5
|
* socket.c: Update copyright according to code changes.Matthias Andree2021-01-031-1/+1
|
* "Require" OpenSSL 1.1.1 and tolerate/warn 1.0.2.Matthias Andree2020-03-301-0/+4
| | | | | | | | | | | OpenSSL 1.0.2 is EOL since end of 2019, so warn if it is to be used at configure and compile time. The assumption is that 1.0.2 may still be in use by maintainers that backport security fixes. Also warn, at configure time, about "OpenSSL" API-compatible libraries that do not declare TLS1_3_VERSION.
* socket.c: add reference to README.SSL in error messageMatthias Andree2020-03-301-1/+2
| | | | | | | and fix a typo in README.SSL. The reference will be printed if there is no trust anchor. Fixes #4 (Gitlab issue).
* Fix garbage at end of plugin string with %h and/or %pMatthias Andree2020-03-291-2/+3
| | | | | | | | | | | Commit 418cda65 from merge request !5 fixed an input buffer overrun but at the same time caused the terminating NUL byte in the output buffer to be written too late, 2 bytes per placeholder. Fix the size calculation for correctness, and use the output index and not the output length to terminate the output string. Fixes #16, reported by Stefan Thurner. [All references for Gitlab.]
* Rename s -> vecsiz (vector size) to hint to its purposeMatthias Andree2020-03-291-4/+4
|
* socket.c: Make SockKeepalive static, and readability variable renames.Matthias Andree2019-09-271-9/+9
|
* Align with legacy_6x.Matthias Andree2019-08-251-4/+10
| | | | | | * Normalize include order. * Backport missed bug fixes. * Remove dead code.
* fetchmail no longer reports System error during SSL_connect(): Success.Matthias Andree2019-08-051-3/+6
| | | | Fixes Debian Bug#928916, reported by Paul Kimoto.
* Bump copyrights, and bump version to beta6.Matthias Andree2019-08-051-1/+4
|
* FreeBSD cleanups to header shuffling.Matthias Andree2019-08-051-4/+1
|
* Replace most strncpy() by strlcpy() calls.Matthias Andree2019-05-121-1/+1
|
* Enable OpenSSL >= 1.0.2 native name verification.Matthias Andree2019-01-271-0/+22
|
* Make compatible with a pure OpenSSL 1.1.0 API, ...Matthias Andree2018-06-061-1/+8
| | | | | ...when deprecated functions are disabled, for instance, through -DOPENSSL_API_COMPAT=0x10100000L.
* Add a FIXME comment.Matthias Andree2017-08-111-0/+2
|
* Do not overrun plugin string when copying it.Alexander Bluhm2017-08-101-1/+1
| | | | | | | | parse_plugin() expands the % in plugin string to plugin_copy. It checks that is does not write behind the end of the destination memory, but the source length was not checked. This resulted in reading from a possibly invalid memory location which may cause a segmentation fault. Add a check for the string length of the source.
* Cast argument to quiet -Wformat warning in C89 mode.Matthias Andree2017-04-231-1/+1
|
* Reformat.Matthias Andree2017-02-111-2/+2
|
* TLS: set hostname for SNI.Matthias Andree2017-02-111-0/+14
|
* Initial TLSv1.3 support code.Matthias Andree2017-02-111-1/+27
|
* Fixup protocol version handling in OpenSSL 1.0.X.Matthias Andree2016-12-121-0/+4
|
* Support for Debian/Ubuntu mutilated SSLv3 support.Matthias Andree2016-12-121-0/+4
| | | | | | | | | | Ubuntu 16.04 LTS, in a misguided attempt to avoid SSLv3 without breaking the API, does not declare SSLv3 unsupported through the headers, so applications can only detect this situation at run-time. The symptom is that SSL_CTX_new errors out with SSL_R_NULL_SSL_METHOD_PASSED on the error stack, issue an additional note telling the user to select a newer version.
* OpenSSL 1.1.0 API support.Matthias Andree2016-12-121-4/+76
| | | | | | | This avoids functions marked deprecated in OpenSSL 1.1.0. At the same time, warn about unsupported use of LibreSSL, and treat LibreSSL the same as OpenSSL 1.0.X WRT protocol version logic.
* Refactor OpenSSL protocol version selection logic.Matthias Andree2016-12-121-44/+54
|
* Bump OpenSSL requirement to v1.0.2.Matthias Andree2016-12-111-2/+2
|
* Really try to continue if OpenSSL lib newer than headers used at compile-time.Matthias Andree2016-04-241-1/+0
|
* Enable TLS 1.1/1.2 options on LibreSSL.Matthias Andree2016-04-241-2/+2
| | | | LibreSSL does not provide a TLS_MAX_VERSION, so do not refer to it.
* Avoid another C99-style comment.Matthias Andree2016-01-301-3/+2
|
* Avoid C99-style comment.Matthias Andree2016-01-301-2/+1
|
* Add OpenSSL version sanity checking.Matthias Andree2016-01-301-1/+24
|
* Support ssl3+ tls1.1, tls1.2 in --sslproto. Report TLS1.1/1.2 if unsupported ↵Matthias Andree2015-04-111-2/+19
| | | | | | by OpenSSL. Uses TLS_MAX_VERSION checks against TLS1_1_VERSION or TLS1_2_VERSION.
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-22 00:08:35 +0000