Code [dev001f]
Tape devices used for backups should not have world permissions.
Code [dev002f]
Devices that have improper (world) permissions might be accessed by any system user. This might open security holes if these are shared devices or hold binaries (disks for example). The administrator should properly set device access (using group configuration to provide access to a device to multiple users, for example).
Code [dev003w]
There is a file in the devices directory which is a common file. Devices directory should only hold special files although some systems have directories and shell scripts in /dev. Please check your system's documentation to determine if that file should be located there.
Code [boot01]
The lilo configuration file (/etc/lilo.conf) should have permissions limiting access to only the owner (usually root).
Code [boot02]
The grub configuration file (/boot/grub/grub.conf) should have permissions limiting access to only the owner (usually root).
Code [boot03w]
A boot loader configuration file could not be found. That means that neither /etc/lilo.conf nor /boot/grub/grub.conf exists.
Code [ptch01f]
AutoRPM has determined that there are updated packages waiting to be installed.
Code [ptch02f]
apt-get has determined that there are updated packages waiting to be installed.
Code [ptch03]
The machine does not appear to be a RedHat or Debian system. This test can currently only determine current patch levels if it can find autorpm or apt-get.
Code [ptch04w]
No patch management tool could be found on the system. The scripts looks for autorpm followed by apt-get. If either one is found it is used to determine if updated packages are available for your system. This message indicates that neither program was found on your system.
Code [ptch05e]
If the Tiger tool is not running as root it will probably not be able to update the package database from the latest sources available. Some errors might be printed on the output and the security check will be done only on the current available list of packages (which might not be up-to-date). Make sure that you are running the tool as an administrative user.
Code [osv001f]
The operating system version appears to be less than RedHat 6.2 Due to security enhancements and fixes available in recent releases, running an older version of RedHat is strongly discouraged.
Code [osv002f]
The operating system version appears to be less than Debian 3.0 Due to security enhancements and fixes available in recent releases, running an older version of Debian is strongly discouraged.
Code [osv003w]
The machine does not appear to be a RedHat or Debian system. This test can not suggest a recommended version number for your operating system.
Code [osv004w]
The machine is running an unreleased version of Debian GNU/Linux. This version is not supported by the security team so it might not be up-to-date security wise (support is only provided for the latest release). That is, "run at your own risk".
Code [sum001f]
The system does not appear to require a password during single-user mode boot. Either add a password to your boot loader or add the line: ~~:S:wait:/sbin/sulogin to your /etc/inittab file. This line should be added immediately before the line containing "rc 0".
Code [trip01f]
Tripwire has detected an inconsistency in the noted file. This file has been modified in some way since the database was built -- either upgraded, removed or tampered with. If this modification is legitimate please refresh the tripwire database by running "tripwire --update"