Date: Wed, 13 Jun 2001 08:25:22 -0700 From: "Sam Leffler" <sam@errno.com> To: "Cy Schubert - ITSD Open Systems Group" <Cy.Schubert@uumail.gov.bc.ca>, "Sheldon Hearn" <sheldonh@starjuice.net> Cc: <freebsd-security@FreeBSD.ORG> Subject: Re: tripwire Message-ID: <0a6301c0f41d$0fb78c10$24a6d4d1@melange> References: <200106131323.f5DDNLU09513@cwsys.cwsent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I thought 2.3.1 was proprietary and source was not available. I'd never have run it in linux emulation mode if I'd located the source... Sam ----- Original Message ----- From: "Cy Schubert - ITSD Open Systems Group" <Cy.Schubert@uumail.gov.bc.ca> To: "Sheldon Hearn" <sheldonh@starjuice.net> Cc: "Sam Leffler" <sam@errno.com>; <freebsd-security@FreeBSD.ORG> Sent: Wednesday, June 13, 2001 6:22 AM Subject: Re: tripwire > In message <68633.992422998@axl.seasidesoftware.co.za>, Sheldon Hearn > writes: > > > > > > On Tue, 12 Jun 2001 21:44:37 MST, "Sam Leffler" wrote: > > > > > Do folks use tripwire or is there a preferred alternative? The LGPL Linux > > > 2.2.1 version works fine in compatibility mode under 4.3-R (after a little > > > tweaking to get it installed). > > > > You can use a native version, as built from the ports tree: > > > > /path/to/ports/tripwire > > /path/to/ports/tripwire-131 > > > > It works very well for many people. Reading the accompanying > > documentation is worthwhile. > > I'm currently working on a tripwire-231 port. It compiles and runs on > FreeBSD using native FreeBSD binaries. I'm about 30% complete on a > FreeBSD-specific policy file. The policy file shipped with the source > is RedHat-specific: Many binaries that exist on RedHat do not exist on > FreeBSD and vice versa. Also many binaries on RedHat that reside in > /bin, /sbin, and /lib reside in /usr/bin, /usr/sbin, and /usr/lib. I > must say that I'm discovering some of the esoteric bits and pieces of > both RedHat and FreeBSD in the translation process. > > If people want, I could shortcut the whole process by creating a > generic policy file similar to the generic nature of the tripwire-131 > policy file. This would give us a tripwire-231 port now and an updated > tripwire-231 port with a FreeBSD-specific policy file later when I've > completed building the FreeBSD policy file. If people see value in > this, I will do it. > > > Regards, Phone: (250)387-8437 > Cy Schubert Fax: (250)387-5766 > Team Leader, Sun/Alpha Team Internet: Cy.Schubert@osg.gov.bc.ca > Open Systems Group, ITSD, ISTA > Province of BC > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0a6301c0f41d$0fb78c10$24a6d4d1>