ANNOUNCE: The 6.4.18-rc1 release candidate #1 of fetchmail is available (SSL change and fetchmailconf regression fix)

Matthias Andree <[email protected]> Sat, 13 Mar 2021 21:18:55 +0100
Newsgroups gmane.mail.fetchmail.announce
Message-ID <YE0eL2l+S6CTbZc7__43106.2688397773$1615666774$gmane$org@ryzen.an3e.de>
--===============8785038629579241862==
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="5Ge5dkCLDRQ/R0nW"
Content-Disposition: inline


--5Ge5dkCLDRQ/R0nW
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Greetings,

The 6.4.18-rc1 release of fetchmail is now available at the usual locations,
including <https://sourceforge.net/projects/fetchmail/files/branch_6.4/>.

Please test this release if you authenticate with an SSL/TLS key file
and certificate, and please test the user configuration screens inside
fetchmailconf if you are a fetchmailconf user, and report any findings,
or report if things continue to work for you.

The source archive is available at:
<https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.=
18-rc1.tar.xz/download>

A detached GnuPG signature is at:
<https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.=
16-rc1.tar.xz.asc/download>

Here are the release notes:

---------------------------------------------------------------------------=
-----
fetchmail-6.4.18 (not yet released):

# REGRESSION FIX:
* fetchmailconf: fetchmail 6.4.16 added --sslcertfile to the configuration =
dump,
  but fetchmailconf support was incomplete in Git 7349f124 and it could not
  parse sslcertfile, thus the user settings editor came up empty with conso=
le
  errors printed.  Fix configuration parser in fetchmailconf.

# ROBUSTNESS FIXES:
* fetchmailconf: do not require fetchmail for -V. do not require Tk (Tkinte=
r)
  for -d option. This is to fail more gracefully on incomplete installs.
* TLS code: remove OPENSSL_NO_DEPRECATED macros to avoid portability issues
  with OpenSSL v3 - these are for development purposes, not production.
* TLS futureproofing: use SSL_use_PrivateKey_file instead of=20
  SSL_use_RSAPrivateKey_file, the latter will be deprecated with OpenSSL v3,
  and the user's key file might be something else than RSA.
---------------------------------------------------------------------------=
-----

Happy fetches,
Matthias

--5Ge5dkCLDRQ/R0nW
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE3EplW9mTzUhx+oIQ5BKxVu/zhVoFAmBNHi8ACgkQ5BKxVu/z
hVrMYA//ZYr0jG29rMIofHAFEp8QFC0ty96W2yU3eqFdVMird6SkkQJ8fpBFmsbM
h4Uda6+SNC+BQEs9GsAjmn27bOraNWMnTnvgIhYzvlpIvlkPZ1JobAwkmgwtlsre
1Pb8u1GmOlOWMVdWsacUXkv0AP0hbTp09kDvCLT8yedU7pITbFJC1dto28GChfw5
ChQVVycPC1jn/f7BbF0lsbexdxSR8o0ElRQkUmbInBHK4zjpRAYkarFz+1rgiNg8
8j2Rsax8iYzyAz6cVn4NNAnSiW9duJWPRHiNGqHwP3Ntscjev+VZTJCwb6nc1Dee
2KcC2PkfelDoRSunFJGTJaETHdSAy7HLbrk11O0F008fYegW8kqecq0XvL5N0l90
dTlRuQHiNdMcYDi0tdwH+Rqe4M4EB7Hzg0KFYa9iazJEDfY80xSYwvLp/lEPozew
hwj0a8W5c7oO0QyRpdeZ8Q0cPSNc4zeceVFzzXaTgvbGDyXF4rANW+mV6h17Kze6
E2i13fMI1/9xlVRURODNLllugzQjjwF2TGVbfOIcu8+11RBNt+AOgfr9m8DhvgUE
FUiyGaPl5nWdN9PPxerzKd7tePc4VoaqkXs5BeVSFgJjFf10G4SNMmjALohM0ufK
rfZjk1dSVDGFsJqpxj/ilutHUEkHR0UnpZhomr4HYr44y097qTc=
=/UMK
-----END PGP SIGNATURE-----

--5Ge5dkCLDRQ/R0nW--


--===============8785038629579241862==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============8785038629579241862==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Fetchmail-announce mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fetchmail-announce

--===============8785038629579241862==--