Bugtraq mailing list archives
Re: Verifying file data integrity using L6
From: jrg () BLODWEN DEMON CO UK (James R Grinter)
Date: Sun, 20 Dec 1998 12:30:05 +0000
Ng Pheng Siong <ngps () POST1 COM> writes:
I've toyed with putting a wrapper around l5 to make it work like tripwire, but that means handling all the integrity database maintenance that tripwire does. In essence, reinventing tripwire. ;-|
This seems to be something that a good backup/archive system[1] ought to be recording whilst it backs up files, so that one could simply run a check of all files on a system against those in the database. (For bonus marks, it could ring alarm bells when a file's checksum has changed whilst the timestamps remain the same. Or allow custom rules and queries to be implemented to monitor what has changed.) James. [1. Unfortunately. I've not met many good backup/archive systems.]
Current thread:
- Verifying file data integrity using L6 gilbert () PGCI CA (Dec 17)
- Re: Verifying file data integrity using L6 Ng Pheng Siong (Dec 18)
- <Possible follow-ups>
- Re: Verifying file data integrity using L6 James R Grinter (Dec 20)
- Re: Verifying file data integrity using L6 Marc SCHAEFER (Dec 20)
- Re: Verifying file data integrity using L6 Curt Sampson (Dec 21)
- Why you should avoid world-writable directories D. J. Bernstein (Dec 21)
- Re: Why you should avoid world-writable directories Darren Reed (Dec 22)
- Re: Why you should avoid world-writable directories Alan Cox (Dec 22)
- Re: Why you should avoid world-writable directories Casper Dik (Dec 23)
- Re: Why you should avoid world-writable directories Martin Forssen (Dec 23)
- Linux PAM (up to 0.64-2) local root compromise Michal Zalewski (Dec 23)
- Re: Linux PAM (up to 0.64-2) local root compromise Savochkin Andrey Vladimirovich (Dec 24)
- 3COM Documentation backdoors in CB3500 Pedro Ribeiro (Dec 23)