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

[Matthias A. <mat...@gm...>]

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 console
  errors printed.  Fix configuration parser in fetchmailconf.

# ROBUSTNESS FIXES:
* fetchmailconf: do not require fetchmail for -V. do not require Tk (Tkinter)
  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 
  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