Date: 20 Jan 2004 19:40:28 -0500 From: Lowell Gilbert <freebsd-security-local@be-well.ilk.org> To: freebsd-security@freebsd.org Subject: Re: mtree vs tripwire Message-ID: <447jzmcewz.fsf@be-well.ilk.org> In-Reply-To: <20040120231918.GS24105@seekingfire.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
Tillman Hodgson <tillman@seekingfire.com> writes:
> On Thu, Jan 15, 2004 at 08:38:55AM -0500, Lowell Gilbert wrote:
> > Gregory Neil Shapiro <gshapiro@freebsd.org> writes:
> > > I use:
> > >
> > > mtree -K sha1digest -c -X mtree.exclude -p / > mtree.out
> <snip>
> > > 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 \
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?447jzmcewz.fsf>