Towards INN 2.5.2 (and 2.6.0)
Julien ÉLIE
julien at trigofacile.com
Sat Jan 23 12:31:53 UTC 2010
> I believe it is time to prepare a release of INN 2.5.2; we have already
> accumulated a *lot* of changes since INN 2.5.1.
For your information, here is what is implemented in CURRENT (INN 2.6.0)
that is not in STABLE (INN 2.5.x).
These changes will only be for INN 2.6.0.
Upgrading from 2.5 to 2.6
The following changes require your full attention because a manual
intervention may be needed:
* Owing to the implementation of RFC 4643 (AUTHINFO USER/PASS) in innd,
if remote peers have to authenticate in order to feed articles, they
now have to send a username (which was previously wrongly optional),
before sending their password. The mandatory username, though
currently unused by innd, can be whatever the remote peer wishes. In
previous versions of INN, inncheck was already complaining when
passwd.nntp contained an empty username associated with a password.
A manual review of authenticated feeds should then be done so as to
ensure that they are properly working.
* The Injection-Date: and Injection-Info: headers are now generated by
nnrpd at injection time instead of the NNTP-Posting-Date:,
NNTP-Posting-Host:, X-Complaints-To: and X-Trace: headers. Local
scripts that were using (for authentication, privacy, etc.) these now
deprecated headers should be updated. Also note that the Path: header
of locally posted articles can also contain the contents of the
deprecated NNTP-Posting-Host: field.
* The two *addnntppostingdate* and *addnntppostinghost* parameters in
inn.conf have been respectively renamed to *addinjectiondate* and
*addinjectionpostinghost*. innupgrade takes care of the modification
only for inn.conf; a manual change will therefore be needed for
readers.conf, if these parameters are overriden in this file.
Changes in 2.6.0
* The NNTP protocol requires a username to be sent before a password
when authentication is used. innd was wrongly allowing only a
password to be sent by authenticated peers. See the note above for
more details.
* The Lines: header is no longer generated by nnrpd at injection time.
* The Injection-Date: header is now generated by nnrpd at injection time
instead of the deprecated NNTP-Posting-Date: header, when
*addinjectiondate* is set to true. Note that *addnntppostingdate* has
been renamed to *addinjectiondate* in inn.conf.
* The Injection-Info: header is now generated by nnrpd at injection time
instead of the deprecated NNTP-Posting-Host: (when
*addinjectionpostinghost* is set to true), X-Complaints-To: and
X-Trace: headers. Note that *addnntppostinghost* has been renamed to
*addinjectionpostinghost* in inn.conf. The Path: header of locally
posted articles now also contains the contents of the
NNTP-Posting-Host: header.
* A few headers are now considered as obsolete by nnrpd at injection
time: NNTP-Posting-Date:, NNTP-Posting-Host:, X-Complaints-To:,
X-Trace:, Also-Control:, Article-Names:, Article-Updates:, and
See-Also: headers.
Besides, nnrpd will similarly reject obsolete sendsys, senduuname and
version control messages.
* The presence of a Subject: header field beginning with "cmsg " no
longer causes an article to be interpreted as a control message by
nnrpd at injection time.
* nnrpd no longer differentiates IHAVE from POST. Articles injected
with IHAVE are now treated as though they were injected with POST.
--
Julien ÉLIE
« La moitié des hommes politiques sont des bons à rien.
Les autres sont prêts à tout. » (Coluche)
More information about the inn-workers
mailing list