From owner-freebsd-security@FreeBSD.ORG Fri Jan 16 07:29:32 2004 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A53DC16A4CF for ; Fri, 16 Jan 2004 07:29:32 -0800 (PST) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8964043D54 for ; Fri, 16 Jan 2004 07:29:31 -0800 (PST) (envelope-from lowell@be-well.ilk.org) Received: from be-well.no-ip.com ([66.30.200.37]) by comcast.net (rwcrmhc12) with ESMTP id <20040116152931014004bpt7e>; Fri, 16 Jan 2004 15:29:31 +0000 Received: by be-well.no-ip.com (Postfix, from userid 1147) id 696F73A; Fri, 16 Jan 2004 10:29:27 -0500 (EST) Resent-To: freebsd-security@freebsd.org Resent-From: Lowell Gilbert Resent-Date: 16 Jan 2004 10:29:26 -0500 X-From-Line: nobody Thu Jan 15 08:38:55 2004 Sender: lowell@be-well.ilk.org To: Gregory Neil Shapiro References: <20040114134215.GA21307@sheol.localdomain> <20040114180931.GA17074@miracle.mongers.org> <20040114182154.GA22444@sheol.localdomain> <20040114182755.GX50342@horsey.gshapiro.net> From: Lowell Gilbert Date: 15 Jan 2004 08:38:55 -0500 In-Reply-To: <20040114182755.GX50342@horsey.gshapiro.net> Message-ID: <44oet5mivk.fsf@be-well.ilk.org> User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Lines: 34 Resent-Message-Id: <20040116152927.696F73A@be-well.no-ip.com> cc: security at FreeBSD Subject: Re: mtree vs tripwire X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Security issues [members-only posting] List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jan 2004 15:29:32 -0000 Gregory Neil Shapiro writes: > > Is your reply from personal experience, or is it the same "Hey, it > > could..." as is my question? If the former, would you elaborate on the > > implementation details? > > I use: > > mtree -K sha1digest -c -X mtree.exclude -p / > mtree.out > > where mtree.exclude is: > > ./home > ./mnt > ./proc > ./tmp > ./var/account > ./var/backups > ./var/db > ./var/imap > ./var/lock > ./var/log > ./var/mail > ./var/run > ./var/spool > ./var/tmp > > Although I am sure there is a better way to do it with mtree, to > see if something has changed, I repeat the process and diff the > output. That would be mtree < mtree.out to have mtree do it itself.