From owner-freebsd-chat Fri Sep 15 13:53:15 2000 Delivered-To: freebsd-chat@freebsd.org Received: from smtp.nwlink.com (smtp.nwlink.com [209.20.130.57]) by hub.freebsd.org (Postfix) with ESMTP id 3383F37B422 for ; Fri, 15 Sep 2000 13:53:14 -0700 (PDT) Received: from utah (jcwells@utah.nwlink.com [209.20.130.41]) by smtp.nwlink.com (8.9.3/8.9.1) with SMTP id NAA09699 for ; Fri, 15 Sep 2000 13:53:13 -0700 (PDT) Date: Fri, 15 Sep 2000 14:06:03 -0700 (PDT) From: "Jason C. Wells" X-Sender: jcwells@utah To: freebsd-chat@FreeBSD.org Subject: Re: Tripwire vs. Mtree In-Reply-To: <20000915133313.A58409@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 15 Sep 2000, Kris Kennaway wrote: > Well, thats not a fundamental problem - you can trivially link mtree > statically. Basically, I think mtree can do everything tripwire can, > but it's a raw tool, not a ready-to-use product and you will have to do > a bit of scripting to use it like that. I have never implemented any type of integrity checking. I know mtree runs on installworld but thats about it. I think I am going to give it a go with the native tool. I do recall the database format as being rather terse. Perhaps user issues will steer me toward tripwire. Thank you, Jason C. Wells To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message