Internet Systems Consortium is pleased to announce that a new bug-fix
release of INN is available at:

https://ftp.isc.org/isc/inn/inn-2.6.5.tar.gz

The MD5 checksum of this release is:

25aa0b6d88f941846463e27b20d8de43

A PGP signature, signatures of SHA-1, SHA-256, and SHA-512 checksums, and
a patch from 2.6.4 to 2.6.5 are available in the same directory.

This is a bug-fix and minor feature release over 2.6.4. Upgrading an
existing INN 2.6.4 installation is as simple as building INN 2.6.5,
running make update, and restarting innd and related programs.

Many thanks to Julien ÉLIE for preparing this release.

Changes in 2.6.5

* A new step in INN development has been achieved with the migration of
the INN project to GitHub. We now make use of the features GitHub
provides: issue tracker, pull requests, continuous integration, a
user-friendly interface to browse the code, etc. Our Subversion
repository has therefore been migrated to Git, and our Trac tickets to
the GitHub issue tracker.

* An up-to-date nocem.ctl file is provided with this release. You
should manually update your nocem.ctl file with the new information
recorded about NoCeM issuers, and make sure the right PGP keys are
present on your system.

* Up-to-date control.ctl and moderators files are provided with this
release. You should manually update them (notably for the fido7.*
hierarchy).

* Added a stricter validation of article numbers given in NNTP commands
so that numbers superior to 2^31 are correctly considered invalid.
Thanks to Richard Kettlewell for the patch.

* Added a check in rc.news for the existence of the *pathrun* directory.
INN won't start until this directory is writable. Previously, it
bailed out quickly after starting, without clear logs about why it
failed.

* Fixed parallel builds using "make -j". Thanks to Richard Kettlewell
for the path.

* nnrpd now properly gathers timer statistics when a compression layer
is active.

* nnrpd now properly discards data received from a news client after a
timeout when a TLS layer is active. It previously tried to read
incoming data before closing the socket, leading to decoding errors
from an underlying compression or SASL layer.

* innfeed and ovdb_stat now generate status reports in valid HTML
syntax.

* Fixed a bug in the buffindexed overview that prevented it from working
on several systems, amongst them FreeBSD. Unsupported, and useless,
permission bits were given to semaphores.

* Fixed the detection of library paths at configure time: multilib
directories (lib32 or lib64) are now also used if they exist, even it
the system does not use multilib. It will notably fix the detection
of the OpenSSL 3.0.0 library.

* The *tlscertfile* parameter in inn.conf now permits the use of a
complete certificate chain, instead of necessarily having to use
*tlscafile* for additional certificates.

* Added support for the new OpenSSL 3.0.0 API, which deprecated a few
functions.

* The inn.conf default value for *tlsprotocols* no longer contains TLS
versions 1.0 and 1.1, which have been deprecated by RFC 8996.

* A new inn.conf parameter has been added to tune the length of the
queue of pending connections to innd, nnrpd and the "ovdb" overview
storage method: the *maxlisten* parameter now permits configuring
their listen backlog, whose previously hard-coded values were 128 for
nnrpd and 25 for the others, which was not high enough for some uses.
The default value is now 128 for all of them, and configurable in
inn.conf. Thanks to Kevin Bowling for the patch.

* The name of seven man pages for routines built in libinn(3) are now
prefixed with libinn_ so as not to consume namespace and conflict with
other packages (notably, the list(3) and uwildmat(3) man pages are now
named libinn_list(3) and libinn_uwildmat(3)).

* Other minor bug fixes and documentation improvements, notably a
revised installation checklist and a section summarizing the most used
configuration at the beginning of a few complex man pages.

--
Russ Allbery (eagle@eyrie.org) <https://www.eyrie.org/~eagle/>

Please post questions rather than mailing me directly.
<https://www.eyrie.org/~eagle/faqs/questions.html> explains why.

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

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

iQEzBAEBCgAdFiEE1zk0tJZ0z1zNmsJ4fYAxXFc23nUFAmIlnQ4ACgkQfYAxXFc2 3nVfpwgAq6SjR+q2H6upTWUot3GJU8oYLPwLtlm8+hEku5Qjd4nB1JLaLF+t/51X 0GTZ9WmewcklkttZ1J/8CTooD+h1Zh/s6eijd/ufPn2XL6p1r/fNJNlbfjIAQjZ8 uOBYhsgyfSXvLNyIu8ZpDlFPYQjzbeARbXhOAFcEaQGtP9BXw4giL1fLMKUFBY/m FDFnbhdgalDX8+7Nohrh9wuUN9BDtLggWAw9elfwnt38sBPf+ZMVhcqgSOD96Ag3 pxsFSpruF6680S0OrunO3OErQ5zyYi/hurMdDaVmvjLliIKe072FWNPnpvQ/plyM /6MJO0TzTfPoLdMCGaHuTgIxsP0Wgw==MXMn
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)