/usr/lib/tiger/doc/passwd.html is in tiger 1:3.2.4~rc1-1.
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 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 | <HR><PRE>
</PRE><HR>
<CENTER><H2> Documents for passwd</H2></CENTER>
<A NAME="pass001w"><P><B>Code [pass001w]</B><P>
The listed username occurs more than once in the same file. This
indicates a configuration problem and should be corrected.
<PRE>
</PRE><HR>
<A NAME="pass002w"><P><B>Code [pass002w]</B><P>
The listed userid (uid) occurs more than once in the same file. This
usually indicates a configuration problem and should be corrected. On
many systems, uid 0 (zero) and uid 1 (one) are often used for multiple
usernames. It is usually to completely disable all of the usernames
except for `root' for uid zero and all of the usernames for uid one.
<PRE>
</PRE><HR>
<A NAME="pass003w"><P><B>Code [pass003w]</B><P>
The listed entry does not have the correct number of fields. This
indicates a configuration problem that should be corrected.
<PRE>
</PRE><HR>
<A NAME="pass004w"><P><B>Code [pass004w]</B><P>
The listed username occurs in separate password sources, but the userid
(uid) is different in them. This can lead to unexpected access to
resources if not corrected.
<PRE>
</PRE><HR>
<A NAME="pass005w"><P><B>Code [pass005w]</B><P>
The listed userid (uid) occurs in separate password sources, but the
usernames are different. This can lead to unexpected access to resources
if not corrected.
<PRE>
</PRE><HR>
<A NAME="pass006w"><P><B>Code [pass006w]</B><P>
The password files have integrity issues as found by 'pwck -r'. This
can lead to looping of password manipulation programs and to authentication
or login issues if not corrected.
<PRE>
</PRE><HR>
<A NAME="pass007w"><P><B>Code [pass007w]</B><P>
Some password controls or constraints are missing. These should be be
applied to all users via their /etc/login.defs configuration values.
<PRE>
</PRE><HR>
<A NAME="pass008e"><P><B>Code [pass008e]</B><P>
The password file was not generated and cannot be analysed. This might
probably happen due to Tiger not running with full administrative access.
<PRE>
</PRE><HR>
<A NAME="pass009f"><P><B>Code [pass009f]</B><P>
The format of a given configuration file used for user (or group)
authentication has some inconsistency that might be a security vulnerability.
<PRE>
</PRE><HR>
<A NAME="pass010w"><P><B>Code [pass010w]</B><P>
The listed groupname occurs more than once in the same file. This
indicates a configuration problem and should be corrected.
<PRE>
</PRE><HR>
<A NAME="pass011f"><P><B>Code [pass011f]</B><P>
The listed username has an empty password string. This will allow any user
to gain access to the account without being prompted for a password.
<PRE>
</PRE><HR>
<A NAME="pass012w"><P><B>Code [pass012w]</B><P>
The listed home directory is specified for multiple users. This can lead to
denial-of-service and unexpected resource usage (i.e. shell initialization
files, etc) if not corrected.
<PRE>
</PRE><HR>
<A NAME="pass013w"><P><B>Code [pass013w]</B><P>
The listed username is not using an acceptable, cryptographic method for the
password hash.
<PRE>
</PRE><HR>
<A NAME="pass014w"><P><B>Code [pass014w]</B><P>
The listed login ID is disabled in some manner ('*' in passwd field, etc),
but the login shell for the login ID is a valid shell (from /etc/shells
or the system equivalent). A valid shell can potentially enable the
login ID to continue to be used. The login shell should be changed
to something that doesn't exist, or to something like /bin/false.
<PRE>
</PRE><HR>
<A NAME="pass015w"><P><B>Code [pass015w]</B><P>
The listed login ID does not have a valid login program or shell.
Usually these are defined in /etc/shells.
<PRE>
</PRE><HR>
<A NAME="pass016w"><P><B>Code [pass016w]</B><P>
The listed login ID should not have "/" (system root directory)
as its home drive. This is a possible security hole.
<PRE>
</PRE><HR>
<A NAME="pass017w"><P><B>Code [pass017w]</B><P>
The listed login ID has a user ID of zero (0) and is not the 'root'
account. This should be checked to see if it is legitimate. In any
case, having login ID's with a user ID of zero tends to lead to security
problems, and should be avoided (except for 'root')
<PRE>
</PRE><HR>
<A NAME="pass018f"><P><B>Code [pass018f]</B><P>
The listed administrative login should have an impossible password.
Files owned by this login ID may reside in critical system directories
and compromise of this account could lead to trojan executables in
typical search paths.
<PRE>
</PRE><HR>
<A NAME="pass19w"><P><B>Code [pass19w]</B><P>
The listed login ID does not have password aging enabled. Good
password management practices indicate that passwords should not
be static, but rather should be changed on a regular basis.
<PRE>
</PRE><HR>
<A NAME="pass20w"><P><B>Code [pass20w]</B><P>
The listed login ID is not configured to use shadow passwords. This
indicates the specified login ID has its cypher text publicly available
and is subject to brute force password cracking, even though shadow
passwords are implimented on the system.
<PRE>
</PRE><HR>
<A NAME="pass021f"><P><B>Code [pass021f]</B><P>
The sudoers files (/etc/sudoers and/or the contents of the /etc/sudoers.d/
directory) have syntax issues as found by 'visudo -c'. This
can lead to the sudo program not working properly and scripts or
users not able to use it to elevate privileges if not correct.
|