From owner-freebsd-security@FreeBSD.ORG Tue Jan 20 16:40:30 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 845BB16A4CE for ; Tue, 20 Jan 2004 16:40:30 -0800 (PST) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D27543D2D for ; Tue, 20 Jan 2004 16:40:29 -0800 (PST) (envelope-from freebsd-security-local@be-well.ilk.org) Received: from be-well.no-ip.com ([66.30.196.44]) by comcast.net (sccrmhc11) with ESMTP id <2004012100402801100j8i0ve>; Wed, 21 Jan 2004 00:40:28 +0000 Received: by be-well.no-ip.com (Postfix, from userid 1147) id 36AEEF; Tue, 20 Jan 2004 19:40:28 -0500 (EST) Sender: lowell@be-well.ilk.org To: freebsd-security@freebsd.org References: <20040114134215.GA21307@sheol.localdomain> <20040114180931.GA17074@miracle.mongers.org> <20040114182154.GA22444@sheol.localdomain> <20040114182755.GX50342@horsey.gshapiro.net> <44oet5mivk.fsf@be-well.ilk.org> <20040120231918.GS24105@seekingfire.com> From: Lowell Gilbert Date: 20 Jan 2004 19:40:28 -0500 In-Reply-To: <20040120231918.GS24105@seekingfire.com> Message-ID: <447jzmcewz.fsf@be-well.ilk.org> Lines: 40 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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: Wed, 21 Jan 2004 00:40:30 -0000 Tillman Hodgson writes: > On Thu, Jan 15, 2004 at 08:38:55AM -0500, Lowell Gilbert wrote: > > Gregory Neil Shapiro writes: > > > I use: > > > > > > mtree -K sha1digest -c -X mtree.exclude -p / > mtree.out > > > > 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. > > I just now tried this: > > [root@athena ~/landmine]# ls -l > total 41746 > -rw-r--r-- 1 root wheel 46 Jan 20 14:58 mtree.exclude > -rw-r--r-- 1 root wheel 42713965 Jan 20 16:19 mtree.out > [root@athena ~/landmine]# mtree < mtree.out > mtree: line 270131: unknown keyword Burg > > I'm fairly certain that that's not the intended result ;-) > > That line, BTW, is just a file name with a space in it: > > link=/opt/SC3U/buildings/Den Burg Bruges.bld > > Am I missing somethign fairly simple? Hmm. I've never had this problem, and when I try to trigger it deliberately, I find that my mtree specification has the spaces in the filenames escaped. e.g., foo\040bar\040baz \