From owner-freebsd-security Mon Mar 5 22:49:29 2001 Delivered-To: freebsd-security@freebsd.org Received: from mr200.netcologne.de (mr200.netcologne.de [194.8.194.109]) by hub.freebsd.org (Postfix) with ESMTP id 0D28037B719 for ; Mon, 5 Mar 2001 22:49:23 -0800 (PST) (envelope-from pherman@frenchfries.net) Received: from husten.security.at12.de (dial-213-168-88-172.netcologne.de [213.168.88.172]) by mr200.netcologne.de (Mirapoint) with ESMTP id ACD30494; Tue, 6 Mar 2001 07:49:19 +0100 (CET) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by husten.security.at12.de (8.11.2/8.11.2) with ESMTP id f266n5J08458; Tue, 6 Mar 2001 07:49:06 +0100 (CET) (envelope-from pherman@frenchfries.net) Date: Tue, 6 Mar 2001 07:49:05 +0100 (CET) From: Paul Herman To: Greg Lewis Cc: Cy Schubert - ITSD Open Systems Group , Rob Simmons , Subject: Re: tripwire In-Reply-To: <20010306151047.A34281@misty.eyesbeyond.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 6 Mar 2001, Greg Lewis wrote: > On Mon, Mar 05, 2001 at 07:58:03PM -0800, Cy Schubert - ITSD Open Systems Group wrote: > > The commercial version, Version 2, which Tripwresecurity has made > > the Linux version of the source available, which I might port to > > FreeBSD as well, > > There were patches to get it working under FreeBSD posted to the > list, should be able to find it in the archives, but I can't > remember the location of the patches off the top of my head. I should just add, this is for the Open Source version of Tripwire only, not the super duper commercial version which Cy was talking about. Open Source version 2.3.1 has _just_ been released (see tripwire.org/sourceforge for downloads) and includes support for FreeBSD. As for the commercial version, I don't see why it wouldn't work under Linux-emu, but Cy probably has more experience with that than I do. -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message