Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-security
Navigation:
Lists: gentoo-security: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-security@g.o
From: darren kirby <bulliver@...>
Subject: Sane default tripwire policy file
Date: Wed, 6 Sep 2006 14:24:42 -0700
I spent several hours yesterday and today fleshing out a proper default policy 
file for Gentoo. Now we don't have use the crappy Redhat version from 2002 
that ships with tripwire. I have made it more 'gentooesque' by arranging the 
files/rules based on the package that installs them rather than their 
function. Now a Gentoo system admin can simply comment out an entire block of 
rules for packages that are not installed. I hope it works well for people, 
and maybe after a bit of tweaking by a dev we can get it bundled with the 
tripwire install. 

 I posted it (along with more explanation) over at gentoo bugzilla[1]. I plan 
to improve it even more, and add rules for commonly installed apps such as 
Apache, MySql, Bind, PHP, syslog-ng, vixie-cron and so on. I will post all my 
revisions on my personal site[2].

[1] http://bugs.gentoo.org/show_bug.cgi?id=34662
[2] http://badcomputer.org/unix/tripwire.pol.gentoo

-d
-- 
darren kirby :: Part of the problem since 1976 :: http://badcomputer.org
"...the number of UNIX installations has grown to 10, with more expected..."
- Dennis Ritchie and Ken Thompson, June 1972
Attachment:
pgptpBsHjegex.pgp (PGP signature)
Navigation:
Lists: gentoo-security: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
OT: Remote Console for Linux boxes?
Next by thread:
libvc unmask
Previous by date:
Re: updated GLSA 200605-08 & php-4.4.3-r1 & EMT64
Next by date:
libvc unmask


Updated Jun 17, 2009

Summary: Archive of the gentoo-security mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.