[pkgsrc/trunk]: pkgsrc/mail/fetchmail fetchmail: Update to 6.1.25

To: pkgsrc-changes-hg%NetBSD.org@localhost
Subject: [pkgsrc/trunk]: pkgsrc/mail/fetchmail fetchmail: Update to 6.1.25
From: triaxx <triaxx%pkgsrc.org@localhost>
Date: Sun, 26 Dec 2021 16:35:42 +0000
details:   https://anonhg.NetBSD.org/pkgsrc/rev/d9f0c20343ed
branches:  trunk
changeset: 771758:d9f0c20343ed
user:      triaxx <triaxx%pkgsrc.org@localhost>
date:      Sun Dec 26 15:28:10 2021 +0000

description:
fetchmail: Update to 6.1.25

upstream changes:
-----------------
fetchmail-6.4.25 (released 2021-12-10, 31653 LoC):

# BREAKING CHANGES:
* Since distributions continue patching for LibreSSL use, which cannot be
  linked legally, block out LibreSSL in configure.ac and socket.c, and
  refer to COPYING, unless on OpenBSD (which ships it in the base system).
  OpenSSL and wolfSSL 5 can be used.  SSL-related documentation was updated, do
  re-read COPYING, INSTALL, README, README.packaging, README.SSL.
* Bump OpenSSL version requirement to 1.0.2f in order to safely remove
  the obsolete OpenSSL flag SSL_OP_SINGLE_DH_USE. This blocks out 1.0.2e and
  older 1.0.2 versions. 1.0.2f was a security fix release, and 1.0.2u is
  publicly available from https://www.openssl.org/source/old/1.0.2/
* Some of the configure.ac fiddling MIGHT have broken cross-compilation
  again. The maintainer does not test cross-compiling fetchmail; if you
  have difficulties, try setting PKG_CONFIG_LIBDIR to the pkg-config path
  containing your target/host libraries, or see if --with-ssl-prefix or
  --with-wolfssl-prefix, or overriding LDFLAGS/LIBS/CPPFLAGS, can help.
  Feedback solicited on compliant systems that are before end-of-life.

# BUG FIXES:
* 6.4.24's workaround for OpenSSL 1.0.2's X509_V_FLAG_TRUSTED_FIRST flag
  contained a typo and would not kick in properly.
* Library and/or rpath setting from configure.ac was fixed.

# ADDITIONS:
* Added an example systemd unit file and instructions to contrib/systemd/
  which runs fetchmail as a daemon with 5-minute poll intervals.
  Courteously contributed by Barak A. Pearlmutter, Debian Bug#981464.
* fetchmail can now be used with wolfSSL 5's OpenSSL compatibility layer,
  see INSTALL and README.SSL. This is considered experimental.
  Feedback solicited.

# CHANGES:
* The getstats.py dist-tool now counts lines of .ac and .am files.
* ./configure --with-ssl now supports pkg-config module names, too. See INSTALL.

# TRANSLATIONS: language translations were updated by these fine people:
(in reverse alphabetical order of language codes so as not to prefer people):
* sv:    Göran Uddeborg [Swedish]
* sq:    Besnik Bleta [Albanian]
* pl:    Jakub Bogusz [Polish]
* ja:    Takeshi Hamasaki [Japanese]
* fr:    Frédéric Marchal [French]
* eo:    Keith Bowes [Esperanto]
* cs:    Petr Pisar [Czech]

# CREDITS:
* Thanks to Corey Halpin for testing release candidates.

--------------------------------------------------------------------------------
fetchmail-6.4.24 (released 2021-11-20, 30218 LoC):

# OPENSSL AND LICENSING NOTE:
> see fetchmail-6.4.22 below, and the file COPYING.

  Note that distribution of packages linked with LibreSSL is not feasible
  due to a missing GPLv2 clause 2(b) exception.

# COMPATIBILITY:
* Bison 3.8 dropped yytoknum altogether, breaking compilation due to a
  warning workaround. Remove the cast of yytoknum to void.  This may cause
  a compiler warning to reappear with older Bison versions.
* OpenSSL 1.0.2: Workaround for systems that keep the expired DST Root CA X3
  certificate in its trust store because OpenSSL by default prefers the
  untrusted certificate and fails.  Fetchmail now sets the
  X509_V_FLAG_TRUSTED_FIRST flag (on OpenSSL 1.0.2 only).
  This is workaround #2 from the OpenSSL Blog.  For details, see both:
  https://www.openssl.org/blog/blog/2021/09/13/LetsEncryptRootCertExpire/
  https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/

  NOTE: OpenSSL 1.0.2 is end of life, it is assumed that the OpenSSL library
  is kept up to date by a distributor or via OpenSSL support contract.
  Where this is not the case, please upgrade to a supported OpenSSL version.

# DOCUMENTATION:
* The manual page was revised after re-checking with mandoc -Tlint, aspell,
  igor. Some more revisions were made for clarity.

# TRANSLATIONS: language translations were updated by these fine people:
* sv:    Göran Uddeborg [Swedish]
* pl:    Jakub Bogusz [Polish]
* fr:    Frédéric Marchal [French]
* cs:    Petr Pisar [Czech]
* eo:    Keith Bowes [Esperanto]
* ja:    Takeshi Hamasaki [Japanese]

--------------------------------------------------------------------------------
fetchmail-6.4.23 (released 2021-10-31, 30206 LoC):

# USABILITY:
* For common ssh-based IMAP PREAUTH setups (i. e. those that use a plugin
  - no matter its contents - and that set auth ssh), change the STARTTLS
  error message to suggest sslproto '' instead.
  This is a commonly reported issue after the CVE-2021-39272 fix in 6.4.22.
  Fixes Redhat Bugzilla 2008160. Fixes GitLab #39.

# TRANSLATIONS: language translations were updated by these fine people:
* ja:    Takeshi Hamasaki [Japanese]
* sr:    Мирослав Николић (Miroslav Nikolić) [Serbian]

--------------------------------------------------------------------------------
fetchmail-6.4.22 (released 2021-09-13, 30201 LoC):

# OPENSSL AND LICENSING NOTE:
* fetchmail 6.4.22 is compatible with OpenSSL 1.1.1 and 3.0.0.
  OpenSSL's licensing changed between these releases from dual OpenSSL/SSLeay
  license to Apache License v2.0, which is considered incompatible with GPL v2
  by the FSF.  For implications and details, see the file COPYING.

# SECURITY FIXES:
* CVE-2021-39272: fetchmail-SA-2021-02: On IMAP connections, without --ssl and
  with nonempty --sslproto, meaning that fetchmail is to enforce TLS, and when
  the server or an attacker sends a PREAUTH greeting, fetchmail used to continue
  an unencrypted connection.  Now, log the error and abort the connection.
  --Recommendation for servers that support SSL/TLS-wrapped or "implicit" mode on
  a dedicated port (default 993): use --ssl, or the ssl user option in an rcfile.
  --Reported by: Andrew C. Aitchison, based on the USENIX Security 21 paper "Why
  TLS is better without STARTTLS - A Security Analysis of STARTTLS in the Email
  Context" by Damian Poddebniak, Fabian Ising, Hanno Böck, and Sebastian
  Schinzel.  The paper did not mention fetchmail.

* On IMAP and POP3 connections, --auth ssh no longer prevents STARTTLS
  negotiation.
* On IMAP connections, fetchmail does not permit overriding a server-side
  LOGINDISABLED with --auth password any more.
* On POP3 connections, the possibility for RPA authentication (by probing with
  an AUTH command without arguments) no longer prevents STARTTLS negotiation.
* For POP3 connections, only attempt RPA if the authentication type is "any".

# BUG FIXES:
* On IMAP connections, when AUTHENTICATE EXTERNAL fails and we have received the
  tagged (= final) response, do not send "*".
* On IMAP connections, AUTHENTICATE EXTERNAL without username will properly send
  a "=" for protocol compliance.
* On IMAP connections, AUTHENTICATE EXTERNAL will now check if the server
  advertised SASL-IR (RFC-4959) support and otherwise refuse (fetchmail <= 6.4
  has not supported and does not support the separate challenge/response with
  command continuation)
* On IMAP connections, when --auth external is requested but not advertised by
  the server, log a proper error message.
* Fetchmail no longer crashes when attempting a connection with --plugin "" or
  --plugout "".
* Fetchmail no longer leaks memory when processing the arguments of --plugin or
  --plugout on connections.
* On POP3 connections, the CAPAbilities parser is now caseblind.
* Fix segfault on configurations with "defaults ... no envelope". Reported by
  Bjørn Mork. Fixes Debian Bug#992400.  This is a regression in fetchmail 6.4.3
  and happened when plugging memory leaks, which did not account for that the
  envelope parameter is special when set as "no envelope". The segfault happens
  in a constant strlen(-1), triggered by trusted local input => no vulnerability.
* Fix program abort (SIGABRT) with "internal error" when invalid sslproto is
  given with OpenSSL 1.1.0 API compatible SSL implementations.

# CHANGES:
* IMAP: When fetchmail is in not-authenticated state and the server volunteers
  CAPABILITY information, use it and do not re-probe. (After STARTTLS, fetchmail
  must and will re-probe explicitly.)
* For typical POP3/IMAP ports 110, 143, 993, 995, if port and --ssl option
  do not match, emit a warning and continue. Closes Gitlab #31.
  (cherry-picked from 6.5 beta branch "legacy_6x")
* fetchmail.man and README.SSL were updated in line with RFC-8314/8996/8997
  recommendations to prefer Implicit TLS (--ssl/ssl) and TLS v1.2 or newer,
  placing --sslproto tls1.2+ more prominently.
  The defaults shall not change between 6.4.X releases for compatibility.

# TRANSLATIONS: language translations were updated by these fine people:
* sq:    Besnik Bleta [Albanian]
* cs:    Petr Pisar [Czech]
* eo:    Keith Bowes [Esperanto]
* fr:    Frédéric Marchal [French]
* pl:    Jakub Bogusz [Polish]
* sv:    Göran Uddeborg [Swedish]

# CREDITS:
* Thanks for testing the release candidates and bug reports to:
  Corey Halpin, Stefan Eßer.CVS: ----------------------------------------------------------------------

diffstat:

 mail/fetchmail/Makefile |  5 ++---
 mail/fetchmail/distinfo |  8 ++++----
 2 files changed, 6 insertions(+), 7 deletions(-)

diffs (30 lines):

diff -r e92d11ad9121 -r d9f0c20343ed mail/fetchmail/Makefile
--- a/mail/fetchmail/Makefile   Sun Dec 26 14:28:00 2021 +0000
+++ b/mail/fetchmail/Makefile   Sun Dec 26 15:28:10 2021 +0000
@@ -1,8 +1,7 @@
-# $NetBSD: Makefile,v 1.200 2021/11/10 19:24:52 khorben Exp $
+# $NetBSD: Makefile,v 1.201 2021/12/26 15:28:10 triaxx Exp $
 
 # Note to updaters: mail/fetchmailconf reaches over here, make sure it builds.
-DISTNAME=      fetchmail-6.4.21
-PKGREVISION=   2
+DISTNAME=      fetchmail-6.4.25
 CATEGORIES=    mail
 MASTER_SITES=  ${MASTER_SITE_SOURCEFORGE:=fetchmail/}
 EXTRACT_SUFX=  .tar.xz
diff -r e92d11ad9121 -r d9f0c20343ed mail/fetchmail/distinfo
--- a/mail/fetchmail/distinfo   Sun Dec 26 14:28:00 2021 +0000
+++ b/mail/fetchmail/distinfo   Sun Dec 26 15:28:10 2021 +0000
@@ -1,8 +1,8 @@
-$NetBSD: distinfo,v 1.61 2021/10/26 10:54:01 nia Exp $
+$NetBSD: distinfo,v 1.62 2021/12/26 15:28:10 triaxx Exp $
 
-BLAKE2s (fetchmail-6.4.21.tar.xz) = 0353dd795872580e40ae93870fc1b7512745c81a52db8fb4b5272faddc94fa2a
-SHA512 (fetchmail-6.4.21.tar.xz) = c9300f63c0e4073f199a9a7d9061774a7f88aad496b696cad96c0ee85107cae506461f0cd083903c60104b1e7654461213f3f759c1cdaffaf1c85fb1956faa67
-Size (fetchmail-6.4.21.tar.xz) = 1318996 bytes
+BLAKE2s (fetchmail-6.4.25.tar.xz) = 042b4b0a4aafb7ffde80e0b0cbd08c8754898919b2f78f9d6c729016a5e385ad
+SHA512 (fetchmail-6.4.25.tar.xz) = 33adbcc1d46f4260a8e74e2a8d2375086374ffa403f7b73a9583db2bfce1319b39d8cceb5127201704344444df5fc33b91097dc0060fa76cb07128889db27434
+Size (fetchmail-6.4.25.tar.xz) = 1343360 bytes
 SHA1 (patch-Makefile.in) = 9cd2053a7c8bbbf6f71fcee03e33c0d29d235c4e
 SHA1 (patch-configure) = f5db59db380755d8b9fc8f75e723fd729ca06c30
 SHA1 (patch-configure.ac) = 9ff885f7d40a749f628d35a8408b1860f8017362
Prev by Date: [pkgsrc/trunk]: pkgsrc/mail/fetchmailconf fetchmailconf: Update to 6.4.25
Next by Date: [pkgsrc/trunk]: pkgsrc/doc doc: Updated mail/fetchmailconf to 6.4.25
Previous by Thread: [pkgsrc/trunk]: pkgsrc/mail/fetchmailconf fetchmailconf: Update to 6.4.25
Next by Thread: [pkgsrc/trunk]: pkgsrc/doc doc: Updated mail/fetchmailconf to 6.4.25
Indexes:
Home | Main Index | Thread Index | Old Index