-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 NotDashEscaped: You need GnuPG to verify this message
It's amazing what a good, strong cup of coffee can do :)
(Note: can sombody please advise me how to submit this to QA? I tried the bugzilla interface, but because "tripwire" is not listed as an FC1 component, it was rejected.)
Tripwire 2.3.1-18.rhfc1 is now ready, approximately 4 days ahead of schedule.
Details:
NAME: tripwire VERSION: 2.3.1 RELEASE: 18.rhfc1
SUMMARY: A system integrity assessment tool.
DESCRIPTION: Tripwire is a very valuable security tool for Linux systems, if it is installed to a clean system. Tripwire should be installed right after the OS installation, and before you have connected your system to a network (before any possibility exists that someone could alter files on your system).<snip>
CHANGELOG:
* Tue Nov 25 2003 Keith G. Robertson-Turner tripwire-devel@genesis-x.nildram.co.uk 2.3.1-18.rhfc1
- Implemented Paul Herman's tw-20030919.patch
- Removed the fhs gcc3 and jbj patches, which are now broken/obsoleted by the above
- Both the mkstemp and rfc822 patches are still implemented
- Build uses autoconf for now
Download:
http://www.genesis-x.nildram.co.uk/filez/tripwire-2.3.1-18.rhfc1.i386.rpm http://www.genesis-x.nildram.co.uk/filez/tripwire-2.3.1-18.rhfc1.i686.rpm http://www.genesis-x.nildram.co.uk/filez/tripwire-2.3.1-18.rhfc1.src.rpm
Note, as the above has not yet passed QA, it should be treated as an unstable beta, however it WorksForMe®.
Comments/Bug submissions: tripwire-devel at genesis-x.nildram.co.uk
- Regards,
Keith G. Robertson-Turner tripwire-devel at genesis-x.nildram.co.uk
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/w2tF2XoLj+pGfn8RAtWMAJ9zIJfKkCYT0Egz6gdFVW1LareUXwCeK344 CBHWop0FAe/MZtDNZomfNbA= =fZqI
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 NotDashEscaped: You need GnuPG to verify this message
tripwire-2.3.1-18.rhfc1 has now been submitted for QA.
https://bugzilla.fedora.us/show_bug.cgi?id=1058
- Keith G. Robertson-Turner tripwire-devel at genesis-x.nildram.co.uk
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Keith,
first thanks for making this updated tripwire rpms available. I just took a quick look at the srpm and could not find:
| - Implemented Paul Herman's tw-20030919.patch
Did you incorporate this patch directly into the tripwire-*.tar.gz file? If this is the case then we have no chance to look at the patch itself. Instead it would be good if you could put the patch separately into the srpm and let the spec file do the patching like it is done for the other patches in the srpm.
Best regards.
- -- Dipl.-Ing. (FH) Bernd Bartmann Bernd.Bartmann@sohanet.de I.S. Security and Network Engineer SoHaNet Technology GmbH / Kaiserin-Augusta-Allee 10-11 / 10553 Berlin Fon: +49 30 214783-44 / Fax: +49 30 214783-46
From: Keith G. Robertson-Turner redhat-forums@genesis-x.nildram.co.uk tripwire-2.3.1-18.rhfc1 has now been submitted for QA.
Thank you....
For tripwire (-17) I have been tinkering with redirecting standard error in /etc/cron.daily/tripwire-check so redundant messages like: ### Warning: File system error. ### Filename: /sbin/fsck.minix Result in a single entry at the end of the report file thus: 2. File system error. Filename: /sbin/fsck.minix No such file or directory
The change I made in /etc/cron.daily/tripwire-check is. Was: test -f /etc/tripwire/tw.cfg && /usr/sbin/tripwire --check Now is: #test -f /etc/tripwire/tw.cfg && /usr/sbin/tripwire --check test -f /etc/tripwire/tw.cfg && /usr/sbin/tripwire --check 2> /dev/null
What larger set of troubles might this generate and what errors am I blindly tossing once tripwire is correctly setup and running? So far I like the result and tripwire does the right thing as far as I can tell. i.e. am I doing something stupid?
Regards, TomM
-
Bernd Bartmann -
Keith G. Robertson-Turner -
Tom Mitchell