	FML Security Advisory 1999-005: How to fix Y2K in old fml packages
	========================================

Topic:		YEAR 2000 Problems

			Ken'ichi Fukamachi <fukachan@sapporo.iij.ad.jp>

	Copyright (C) 1999 Ken'ichi Fukamachi
		All rights reserved.

[Abstract]

Best current practise on fml y2k.

"Please use current" is always true answer.

------------------------------------------------------------
1	Tools to fix

2	Overview

3	Date: field

4	Log file format
4.1	Overview
4.2	How to fix

5	RFC1153 mode
------------------------------------------------------------


1	Tools to fix

	ftp://ftp.iij.ad.jp/pub/IIJ/dist/fukachan/fml/y2k-fix.tar.gz

   % cp -pr /usr/local/fml /usr/local/fml.bak

   % perl -i.bak fix-gettime.pl /usr/local/fml/*pl

   % chmod 755 /usr/local/fml/fml.pl /usr/local/fml/msend.pl

2	Overview

Fml uses unix time internally, so fml will have no y2k problem except
for header and log files. Fml uses &GetTime as date translation, so we
should check only this function.

If you fix problems around date, hack 'sub GetTime' function. 
For example

sub GetTime
{

	...

}

3	Date: field

must be O.K. after 2.2.1.

fml.pl revision: 1997/12/07 fml.pl 2.0.24.49

4	Log file format

must be O.K. after 2.2.1.

4.1	Overview

4.2	How to fix

fml.pl revision: 2.2.1.7 (1998/11/06)

fml.pl revison: 2.12 (1999/02/13)

5	RFC1153 mode

This problem is not fixed after fml 2.2.1 release. But RFC1153 is
ambiguous. I have no correct idea how to fix rfc1153 mode...
fml rfc1153 library appends rather date to 1153-like identifier, so
we should rewrite librfc1153.pl completely.

