Package: tripwire Version: 2.4.2-9 Severity: minor Tags: upstream
After changing a monitored part of the system, one runs tripwire -m c -I Even accepting all changes, the next time a check is run it fails again if the command was issued from a monitored directory. It is not uncommon to fall into such trap, as the user might had cd there to operate the changes. The correct sequence is pushd /tmp tripwire -m c -I (assuming /tmp is not monitored.) See also bug #353062 Tripwire creates a temporary file in the current directory in order to run the check. It should create it into /tmp. -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- Configuration Files: /etc/cron.daily/tripwire changed [not included] /etc/tripwire/twcfg.txt changed [not included] /etc/tripwire/twpol.txt changed [not included] -- debconf information: * tripwire/installed: tripwire/site-passphrase-incorrect: false * tripwire/use-localkey: true tripwire/change-in-default-policy: tripwire/upgrade: true * tripwire/rebuild-policy: true * tripwire/rebuild-config: true tripwire/email-report: tripwire/broken-passphrase: * tripwire/use-sitekey: true tripwire/local-passphrase-incorrect: false -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
