From mboxrd@z Thu Jan 1 00:00:00 1970 From: Theodore Ts'o Subject: Re: Data Integrity Check on EXT Family of Filesystems Date: Tue, 24 Sep 2013 10:57:24 -0400 Message-ID: <20130924145724.GA13407@thunk.org> References: <5856b37a-3b66-4404-a6f7-3c120b14ae95@zimbra> <956c398f-5500-433a-a423-ebb96a20c468@zimbra> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Andrew Martin , linux-fsdevel@vger.kernel.org To: Mike Fleetwood Return-path: Received: from imap.thunk.org ([74.207.234.97]:37082 "EHLO imap.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753565Ab3IXO51 (ORCPT ); Tue, 24 Sep 2013 10:57:27 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Mon, Sep 23, 2013 at 11:00:09PM +0100, Mike Fleetwood wrote: > > Here's a couple of integrity checking tools to consider: > tripwire - http://sourceforge.net/projects/tripwire/ > aide - http://aide.sourceforge.net/ I use cfv myself to create checksum files. Note that using CRC checksum is plenty if you are just worried about random corruption caused by hardware errors (i.e., memory bitflips, hard drive hiccups). Using a cryptographic checksum ala tripwire is useful if you are worried about malicious attackers trying to modify files without your noticing. Cryptographic checksums do take more CPU time, though. Cheers, - Ted