Summary: | app-admin/mktwpol-0.2.2 - Error: Rule already defined as a start or stop point of another rule | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Adam Randall <randalla> |
Component: | Current packages | Assignee: | Chema Alonso Josa (RETIRED) <nimiux> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | c.cboldt, randalla |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Adam Randall
2014-02-07 16:55:46 UTC
The file /etc/security/limits.conf is entered twice on your system (and not on mine) becuase you have installed the "pam" package. This is obviously common, and I think my decision to specifically name /etc/security/limits.conf for creation of a policy was an unwise decision. mktwpol.sh -u will deliver a policy file without the reported error, if you change /etc/tripwire/mktwpol-gentoo-140202.rules file as follows: COMMENTS[1]='Security Control Files' FILELIST[1]="/etc/security" This change removes the specific listing of /etc/security/limits.conf in FILELIST[1]. Tripwire will continue to monitor files in the /etc/security branch, and /etc/security/limits.conf will be specifically listed (in your policy) under the "pam" package. Thanks for the report. Thanks for the feedback. I'll try out your suggestion here in a little while once I undig myself from my current tasks. Yes, that did resolve my issue. |