Projects / Easy Integrity Check System

Easy Integrity Check System

Easy integrity check system is an easy-to-install and use file integrity system. It is intended to be used by system administrators to aid with intrusion detection.

Tags Security
Licenses GPL
Operating Systems POSIX
Implementation C

Tweet this project Short link

Rss Recent releases

  • Rrelease-mid
  •  05 Apr 2005 06:50
  • Rrelease-after

Changes: A critical bug that manifested itself after creating release 3.1b was fixed. If you downloaded the previous version, you should replace it with this version.

  • Rrelease-mid
  •  05 Apr 2005 06:50
  • Rrelease-after

Changes: A database handling bug has been fixed. It prevented the database from being updated under certain conditions.

  • Rrelease-mid
  •  15 Jul 2004 07:06
  • Rrelease-after

Changes: Two issues has been fixed. Firstly, an occasional bug that where the system refuses to update the database even when inconsistency is detected was fixed. The Makefile was also updated to avoid overwriting eics.conf if such a file already exists.

  • Rrelease-mid
  •  20 Jun 2004 18:36
  • Rrelease-after

Changes: This is a complete rewrite. The new system features improved checking code, faster lookup time from internal structures, regular expression support, better coupling with OpenSSL, and faster overall performance.

  • Rrelease-mid
  •  23 May 2003 01:58
  • Rrelease-after

Changes: This version features minor fixes, removes pcre.h, which was forgotten, and fixes handling of symbolic links to not generate a warning from wrong filename for inodes.

Rss Recent comments

Rcomment-before 23 Jun 2004 04:39 Rcomment-trans ievlev Rcomment-after

Re: Interesting project.

>

>

> Thank you for your comment. The reason I

> use my own database is that it allows me

> to store the data as compact as possible

> and also allows me to control better

> what is stored. I'm sure the CDB system

> is fast and everything, but I doubt it

> comes any faster since I preload

> everything into memory before starting

> to process. The in-memory data is stored

> in more or less efficient hashtable

> allowing near O(1) acccess times.

CDB mmap() all data into memory, so it's fast

enough.

This is very efficient, 'cause it is a Constant

(Read-only or Write-only).

It also uses hashtable to made access faster.

Size of database is small, cause it have

read-only/write-only design.

Rcomment-before 21 Jun 2004 02:09 Rcomment-trans cmouse Rcomment-after

Re: Interesting project.

> Hi! Interesting work. Good idea to use

> openssl

> for digests.

>

> As I understand you use own database

> format,

> to store file data (checksums,stat

> information,etc.).

>

> It may be interesting for you:

> http://freshmeat.net/projects/o-security/

>

>

> osec - it's mine integrity checker, that

> uses CDB

> for database. CDB works faster then

> others.

>

>

Thank you for your comment. The reason I use my own database is that it allows me to store the data as compact as possible and also allows me to control better what is stored. I'm sure the CDB system is fast and everything, but I doubt it comes any faster since I preload everything into memory before starting to process. The in-memory data is stored in more or less efficient hashtable allowing near O(1) acccess times.

Rcomment-before 21 Jun 2004 01:54 Rcomment-trans ievlev Rcomment-after

Interesting project.
Hi! Interesting work. Good idea to use openssl

for digests.

As I understand you use own database format,

to store file data (checksums,stat

information,etc.).

It may be interesting for you:

http://freshmeat.net/projects/o-security/

osec - it's mine integrity checker, that uses CDB

for database. CDB works faster then others.

3aabfbf462d3cedff093bdb7f8cf5fa8_thumb

Project Spotlight

Pidgin

A GTK2-based instant messaging client.

2be54b71297039335b98ef9a39642044_thumb

Project Spotlight

Grsync

A GUI for rsync using GTK.