/usr/lib/tiger/doc/pxt.html is in tiger 1:3.2.3-10.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 | <HR><PRE>
</PRE><HR>
<CENTER><H2> Documents for pxt</H2></CENTER>
<A NAME="dev001f"><P><B>Code [dev001f]</B><P>
Tape devices used for backups should not have world permissions.
<PRE>
</PRE><HR>
<A NAME="dev002f"><P><B>Code [dev002f]</B><P>
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).
<PRE>
</PRE><HR>
<A NAME="dev003w"><P><B>Code [dev003w]</B><P>
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.
<PRE>
</PRE><HR>
<A NAME="boot01"><P><B>Code [boot01]</B><P>
The lilo configuration file (/etc/lilo.conf) should have permissions
limiting access to only the owner (usually root).
<PRE>
</PRE><HR>
<A NAME="boot02"><P><B>Code [boot02]</B><P>
The grub configuration file (/boot/grub/grub.conf) should have
permissions limiting access to only the owner (usually root).
<PRE>
</PRE><HR>
<A NAME="boot03w"><P><B>Code [boot03w]</B><P>
A boot loader configuration file could not be found. That means
that neither /etc/lilo.conf nor /boot/grub/grub.conf exists.
<PRE>
</PRE><HR>
<A NAME="ptch01f"><P><B>Code [ptch01f]</B><P>
AutoRPM has determined that there are updated packages waiting
to be installed.
<PRE>
</PRE><HR>
<A NAME="ptch02f"><P><B>Code [ptch02f]</B><P>
apt-get has determined that there are updated packages waiting
to be installed.
<PRE>
</PRE><HR>
<A NAME="ptch03"><P><B>Code [ptch03]</B><P>
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.
<PRE>
</PRE><HR>
<A NAME="ptch04w"><P><B>Code [ptch04w]</B><P>
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.
<PRE>
</PRE><HR>
<A NAME="ptch05e"><P><B>Code [ptch05e]</B><P>
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.
<PRE>
</PRE><HR>
<A NAME="osv001f"><P><B>Code [osv001f]</B><P>
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.
<PRE>
</PRE><HR>
<A NAME="osv002f"><P><B>Code [osv002f]</B><P>
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.
<PRE>
</PRE><HR>
<A NAME="osv003w"><P><B>Code [osv003w]</B><P>
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.
<PRE>
</PRE><HR>
<A NAME="osv004w"><P><B>Code [osv004w]</B><P>
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".
<PRE>
</PRE><HR>
<A NAME="sum001f"><P><B>Code [sum001f]</B><P>
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".
<PRE>
</PRE><HR>
<A NAME="trip01f"><P><B>Code [trip01f]</B><P>
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"
|