head	1.1;
access;
symbols
	RELEASE_8_3_0:1.1
	RELEASE_9_0_0:1.1
	RELEASE_7_4_0:1.1
	RELEASE_8_2_0:1.1
	RELEASE_6_EOL:1.1
	RELEASE_8_1_0:1.1
	RELEASE_7_3_0:1.1
	RELEASE_8_0_0:1.1
	RELEASE_7_2_0:1.1
	RELEASE_7_1_0:1.1
	RELEASE_6_4_0:1.1
	RELEASE_5_EOL:1.1
	RELEASE_7_0_0:1.1
	RELEASE_6_3_0:1.1
	PRE_XORG_7:1.1
	RELEASE_4_EOL:1.1
	RELEASE_6_2_0:1.1
	RELEASE_6_1_0:1.1
	RELEASE_5_5_0:1.1
	RELEASE_6_0_0:1.1
	RELEASE_5_4_0:1.1
	RELEASE_4_11_0:1.1
	RELEASE_5_3_0:1.1
	RELEASE_4_10_0:1.1
	RELEASE_5_2_1:1.1
	RELEASE_5_2_0:1.1
	RELEASE_4_9_0:1.1
	RELEASE_5_1_0:1.1
	RELEASE_4_8_0:1.1
	RELEASE_5_0_0:1.1
	RELEASE_4_7_0:1.1;
locks; strict;
comment	@# @;


1.1
date	2002.07.07.04.51.26;	author cy;	state Exp;
branches;
next	;


desc
@@


1.1
log
@Add l5 1.2, file Integrity Assessment Tool.

PR:		39970
Submitted by:	andrew@@scoop.co.nz
@
text
@After examining Tripwire and deciding that it was *way* overkill for my
own purposes...

...L5 simply walks down Unix or DOS filesystems, sort of like "ls -R" or
"find" would, generating listings of anything it finds there.  It tells
you everything it can about a file's status, and adds on an MD5 hash of
it.  Its output is rather "numeric", but it is a very simple format and
is designed to be post-treated by scripts that call L5...

...Unlike Tripwire itself, this is NOT a complete toolkit -- one is
expected to use it as a small, reliable part of a larger system...

_H*

Andrew McNaughton <andrew@@scoop.co.nz>
@
