TLS: bump library version requirements

to OpenSSL 1.1.1q and 3.0.7 (warning only)
and WolfSSL 5.4.0 (force break build)

1 files changed, 6 insertions, 6 deletions

diff --git a/README.SSL b/README.SSL
index c0e4e2bf..bcc2070a 100644
--- a/README.SSL
+++ b/README.SSL
@@ -21,7 +21,7 @@ below and in the manual).
 
 fetchmail 6.4.0 will auto-negotiate TLSv1 or newer only.
 
-Fetchmail 6.4.25 supports OpenSSL 3.0.5 and 1.1.1q and WolfSSL 5.4.0 or newer.
+Fetchmail 6.4.35 supports OpenSSL 3.0.7 and 1.1.1s and WolfSSL 5.4.0 or newer.
 Note that WolfSSL 5 is a bit less flexible about its trust store,
 see INSTALL chapter 2.1 for details.
 
@@ -29,16 +29,16 @@ Note that many messages printed by fetchmail will print "OpenSSL"
 even if wolfSSL is being used. Reason is that fetchmail uses
 wolfSSL's OpenSSL compatibility layer and not the native wolfSSL API.
 
-	-- Matthias Andree, 2021-12-05
+	-- Matthias Andree, 2022-11-01
 
 
 Quickstart
 ----------
 
-Use an up-to-date release of OpenSSL v1.1.1 or v3.0 or wolfSSL 5.4.0 or
-newer, so as to get TLSv1.3 support.  Older OpenSSL versions are unsupported
-upstream, and fetchmail rejects versions before v1.0.2f and warns about
-versions before v1.1.1.
+Use an up-to-date release of OpenSSL v1.1.1 or v3.0 or wolfSSL 5.4 or
+newer, so as to get TLSv1.3 support and latest fixes.  Older OpenSSL versions 
+are unsupported upstream, and fetchmail rejects versions before v1.0.2f and 
+warns about versions before v1.1.1.
 
 wolfSSL needs to be configured with --enable-opensslall --enable-harden,
 else some required OpenSSL APIs are missing, especially for SNI (server name