Y2K-Bug in INN 1.x, 2.x

[Per Hedeland]

list-inn-workers at news.cistron.nl (Miquel van Smoorenburg) wrote:
>In article <cistron.200001051138.MAA03180 at aalborg.du.uab.ericsson.se>,
>Per Hedeland  <per at erix.ericsson.se> wrote:
>>The proper thing IMHO is of course to use "closest century", a.k.a.
>>standard "sliding window" technique.
>
>Not only IYHO, but in the FRNSHO (Fine RFCs Not So Humble Opinion) as well :)
>See RFC977, paragraph 3.7.1

Yes, it's a FO:-), though strictly speaking 977 has no bearing on the
parsing of Date headers (anyone care to check USEFOR?:-) - and worse,
the nntpext draft slated to update/replace 977 changes this algorithm to
an IMHO:-) broken one, that may give the poor user whose computer time
is a "tad" ahead the last 100 years of newgroups in response to
NEWGROUPS (not to mention what NEWNEWS will give once it starts
working...). And in fact this IMHO-broken algorithm is already
implemented for NEWGROUPS/NEWNEWS in current INN, see
nnrpd/misc.c/NNTPtoGMT().

--Per Hedeland
per at erix.ericsson.se