Red Hat Bugzilla – Bug 51332
Poor defaults for tripwire
Last modified: 2007-03-26 23:47:50 EDT
Description of Problem: Installed roswell (all packages). Tripwire was apparently included & configured into the daily cron job. Email to root indicates it is not set up properly (and sort of explained how...). Did the first step... /etc/tripwire/twinstall.sh No indication after that was complete that more was needed to be done. Email to root the next day.... Did the second step... tripwire --init Error seen as follows... ### Error: File could not be opened. ### Filename: /usr/sbin/tw.cfg ### No such file or directory ### Configuration file could not be read. ### Exiting... OK, tried this... cp /etc/tripwire/tw.cfg /usr/sbin/tw.cfg tripwire --init A gazillion messages ensue some time later [see attachment]. At this point, I'm wondering if I should turn it off, or if I really got it installed OK. I guess I'll find out tomorrow. Can the defaults be improved to either (or all)... [1] when added to cron.daily, require configuration (or at least tell me it is needed during installation) [2] make the default configuration match what Red Hat 7.2 installs How Reproducible: Install "all packages" in roswell and follow the description above. Steps to Reproduce: 1. [see above] 2. 3. Actual Results: See above & attachment. Expected Results: Tripwire be properly configured prior to addition to cron.daily. Additional Information:
Created attachment 27054 [details] Errors from tripwire --init
We (Red Hat) should really try to fix this before next release.
Nalin, you commented something to me about tripwire a week ago or so, was this the problem fixed?
Oops, yes. This should be fixed in 2.3.1-5 and later. Marking as MODIFIED for verification.
Thanks Nalin.