Home / afick
Name Modified Size InfoDownloads / Week
Parent folder
3.8.1 2024-09-12
3.8.0 2023-06-11
3.7.0 2020-11-06
3.6.1 2018-12-14
3.6.0 2017-12-08
3.5.3 2017-02-10
3.5.2 2016-08-05
3.5.1 2015-12-04
3.5.0 2015-05-13
3.4.3 2015-01-12
3.4.2 2014-12-10
3.4.1 2014-11-20
3.4 2013-08-26
3.3 2012-12-21
3.2 2012-11-19
2.22 2012-11-09
3.1 2012-07-20
2.21 2012-07-13
2.20 2012-02-05
2.19 2011-11-10
2.18 2011-10-07
2.17 2011-06-08
2.16-1 2010-12-10
2.15-1 2010-08-01
2.14-1 2009-09-28
2.13-1 2009-01-16
2.12-1 2008-10-20
2.11-1 2008-04-11
2.10-1 2007-05-23
2.9-1 2006-10-04
2.9-0 2006-09-04
2.8-3 2006-07-11
2.8-2 2005-08-18
2.8-1 2005-06-28
2.8-0 2005-06-06
2.7-1 2005-05-03
2.7-0 2005-02-17
Totals: 37 Items   17
goal
----
the goal of this project is to write another file integrity checker :
- portable without any change to all common os (unix, windows)
- with a minimum of dependencies
- quick
- config file with exceptions and "jokers"
- display new, delete and modified files
- use by any user
- any number of base and config files
- syntaxe close from aide's or tripwire's one

history
-------
I was using integrity checking tools on linux (aide) for a long time. So when I
got my first PC on windows, I search for a similar tool (freeshmeat), but do not
find anything ready to use.

I then decided to write my own, with the goal below.
my choice are :
perl as language : for portability, no need to compile, acces to source code
MD5 for checksum : quick and in perl standard package
sdbm database for storage : not clear text, ease of use

I test it on windows XP, redhat linux 7.1 and 7.3
and it seems as fast as a C tool (aide) (see http://afick.sourceforge.net/perf.html)

config file format :
--------------------
see afick.conf man page or comments in config file sample (linux.conf, windows.conf)

usage
-----
1) first choice what you want to check. a base is given in file 
- windows.conf (for windows xp)
- linux.conf (for linux)
you may edit and modify this file for your needs
(please send me your changes if they may help others users)

2) then create the database :
./afick -c your_config_file -i

3) compare regulary your filee with the database (each day ?). You have 3 possibilities :

3.1) just check some files
./afick -c your_config_file -l "file1 $file2  ...filen"

3.2) check all your config 
./afick -c your_config_file -k

3.3) check your config and update the database
./afick -c your_config_file -u

4) you can print the content of the database with 
./afick -c your_config_file -p

main site
---------
the main page for afick project is http://afick.sourceforge.net

--
$Id: README 869 2006-07-10 11:21:46Z gerbier $
Source: README, updated 2011-06-09