This file is indexed.

/usr/lib/tiger/doc/permissions.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
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
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
<HR><PRE>








</PRE><HR>
<CENTER><H2> Documents for permissions</H2></CENTER>
<A NAME="perm001a"><P><B>Code [perm001a]</B><P>
The owner of the indicated file is not correct. This is a serious security
problem and may indicate that an intrusion has occurred. The system should
be checked and cleaned. The owner of the file should be corrected.
<PRE>










</PRE><HR>
<A NAME="perm001f"><P><B>Code [perm001f]</B><P>
The owner of the indicated file is not correct. With the incorrect ownership,
a vulnerability may exist. The owner of the file should be corrected.
<PRE>










</PRE><HR>
<A NAME="perm001w"><P><B>Code [perm001w]</B><P>
The owner of the indicated file is not what is considered best for security
reasons. Unless you have a specific reason for not changing the ownership,
this should be corrected.
<PRE>










</PRE><HR>
<A NAME="perm002a"><P><B>Code [perm002a]</B><P>
The group owner of the indicated file is not correct. This is a serious
security problem and may indicate that an intrusion has occurred. The
system should be checked and cleaned. The group owner of the file should be
corrected.
<PRE>










</PRE><HR>
<A NAME="perm002f"><P><B>Code [perm002f]</B><P>
The group owner of the indicated file is not correct. With the incorrect
group ownership, a vulnerability may exist. The group owner of the file
should be corrected.
<PRE>










</PRE><HR>
<A NAME="perm002w"><P><B>Code [perm002w]</B><P>
The group owner of the indicated file is not what is considered best for
security reasons. Unless you have a specific reason for not changing the
ownership, this should be corrected.
<PRE>










</PRE><HR>
<A NAME="perm003a"><P><B>Code [perm003a]</B><P>
The access permissions of the indicated file are incorrect. This may
indicate an intrusion has occurred. In any event, it is a serious security
problem and should be corrected immediately. The system should also be
checked for signs of intrusion.
<PRE>










</PRE><HR>
<A NAME="perm003f"><P><B>Code [perm003f]</B><P>
The access permissions of the indicated file are incorrect. This may
create a vulnerability in the system. This should be corrected immediately.
<PRE>










</PRE><HR>
<A NAME="perm003w"><P><B>Code [perm003w]</B><P>
The access permissions of the indicated file are not what is considered
best for security. Unless you have a reason for not doing so, the permissions
should be corrected.
<PRE>










</PRE><HR>
<A NAME="perm004c"><P><B>Code [perm004c]</B><P>
No file permissions database can be found. This will prevent the
checks of file ownerships to be performed. This likely indicates
that a complete port has not been done for this platform.
<PRE>










</PRE><HR>
<A NAME="perm005a"><P><B>Code [perm005a]</B><P>
The /etc/security directory contains security information that should
not be accessible by non-root users. The owner should be root, and group
and world should have only search access (mode 711). The directory
unfortunately must be search-able because of some library routines which
check for the existence of the security.adjunct file. The files in the
directory should be mode 600.
<PRE>










</PRE><HR>
<A NAME="perm006w"><P><B>Code [perm006w]</B><P>
The configuration files (.login, .profile, etc) should be not be writable
by non-root users. In addition, the .rhosts file should not be readable
or writable by non-root users.
<PRE>










</PRE><HR>
<A NAME="perm007f"><P><B>Code [perm007f]</B><P>
The /etc/aliases, /etc/aliases.dir and /etc/aliases.pag files should not
be writable by non-root users. On SunOS 4 systems, these files are
shipped world writable. The permissions should be 644 on all three
files. If left writable, program aliases can be added which can
allow unauthorized access.
<PRE>










</PRE><HR>
<A NAME="perm008w"><P><B>Code [perm008w]</B><P>
The /etc/exports (or equivalent) file should not be writable by anyone
other than root. If a non-root user can modify the file, unauthorized
privileges can be obtained. There is also no reason for this file
to be readable by anyone other than root. Making it unreadable, reduces
the information available to an intruder attempting to gain privileged
access.
<PRE>










</PRE><HR>
<A NAME="perm009f"><P><B>Code [perm009f]</B><P>
The /etc/group file should not be writable by anyone other than root.
If a non-root user can modify the file, unauthorized privileges can
be obtained.
<PRE>










</PRE><HR>
<A NAME="perm010w"><P><B>Code [perm010w]</B><P>
The /etc/hosts.allow and /etc/hosts.deny files (from Wietse Venema's
tcp_wrapper package) should not be writable by non-root users. If
they are writable, the protection provided by the package can be
bypassed. In addition, if all of the daemons protected by tcp_wrapper
run as `root', then the file does not need to be readable by non-root
users. Making the permissions 600, reduces the information available
to an intruder attempting to gain privileges. If any daemons are
run as non-root users though, this is not possible.
<PRE>










</PRE><HR>
<A NAME="perm011w"><P><B>Code [perm011w]</B><P>
The /etc/hosts.equiv and /etc/hosts.lpd files define trusted hosts.
The hosts.equiv file defines the trusted hosts for the Berkeley 'R'
commands (rsh, rlogin), while the hosts.lpd file defines trusted hosts
for the print system. If the hosts.equiv or hosts.lpd file is writable
by users other than root, then unauthorized privileges or access may
be gained. In addition, there is no reason for non-root users to be
able to read these files. Making them unreadable reduces the information
available to an intruder attempting to gain privileges.
<PRE>










</PRE><HR>
<A NAME="perm012w"><P><B>Code [perm012w]</B><P>
The /etc/inetd.conf file defines the network daemons controlled by
`inetd'. If this file is writable by non-root users, then unauthorized
access can be obtained. In addition, it is not necessary that this file
be readable by non-root users. Making the file unreadable reduces the
information available to an intruder attempting to gain privileges.
<PRE>










</PRE><HR>
<A NAME="perm013f"><P><B>Code [perm013f]</B><P>
The /etc/netgroup file defines network groups which consist of machines
and users. Allowing write access can allow unauthorized access or
privileges.
<PRE>










</PRE><HR>
<A NAME="perm014a"><P><B>Code [perm014a]</B><P>
If /etc/passwd is writable by non-root users, then new login id's
can be added to the system. Unauthorized access or privileges can
easily be obtained. If the file is world writable, this is a possible
indication that the system has been compromised. The system should
be checked for other signs of intrusion.
<PRE>










</PRE><HR>
<A NAME="perm015f"><P><B>Code [perm015f]</B><P>
The 'rc.*' scripts are executed during system startup. If they are
writable by non-root users, then unauthorized access or privileges can
be obtained. In addition, there is no need for these files to be world
readable. Making them unreadable reduces the information available to
an intruder attempting to gain privileges.
<PRE>










</PRE><HR>
<A NAME="perm016w"><P><B>Code [perm016w]</B><P>
The /etc/resolv.conf file is used to designate where Domain Name
Service is to be obtained. If this file is writable by non-root
users, then unauthorized access or privileges may be obtained.
This file does need to be world readable however.
<PRE>










</PRE><HR>
<A NAME="perm017w"><P><B>Code [perm017w]</B><P>
The /etc/utmp file should not be writable by non-root users. This
is a security vulnerability. Unfortunately, on SunOS 4 systems, the
SunView and OpenWindows 'cmdtool' and 'shelltool' programs do not
function correctly if it is not. If you are not using these tools,
then you should set the permissions to 644.
<PRE>










</PRE><HR>
<A NAME="perm018a"><P><B>Code [perm018a]</B><P>
The root directory should be protected from changes by non-root users.
If the directory is writable by non-root users, unauthorized access
or privileges can be obtained.
<PRE>










</PRE><HR>
<A NAME="perm019a"><P><B>Code [perm019a]</B><P>
The /etc directory should be owned by root and should not be writable
by group or world. As shipped, SunOS 4 systems have the /etc directory
owned by the user `bin'. This is *incorrect*.
<PRE>










</PRE><HR>
<A NAME="perm020w"><P><B>Code [perm020w]</B><P>
The indicated disk device file is world readable, writable or both. This
allows the file access controls to be bypassed. The world permissions
should be removed.
<PRE>










</PRE><HR>
<A NAME="perm021w"><P><B>Code [perm021w]</B><P>
The indicated disk device file is group readable, writable or both by the
indicated group. This allows users in this group to bypass the file
access controls. Many systems allow a group such as `operator' to have
read access so that backups can be performed. Group write access is
*not* needed and should be removed. If backups are performed by the
`root' account, then group read permissions are not needed and should
be removed.
<PRE>










</PRE><HR>
<A NAME="perm022w"><P><B>Code [perm022w]</B><P>
The indicated disk device file is not owned by `root'. This allows the
owner of the disk device to bypass the systems file access controls.
The owner should be changed to `root'.
<PRE>










</PRE><HR>
<A NAME="perm023a"><P><B>Code [perm023a]</B><P>
The indicated file has the setuid bit set, but it should not have it.
This should be changed by using 'chmod u-s file' where 'file' is the
indicated file. The system should be checked for signs of intrusion.
<PRE>










</PRE><HR>
<A NAME="perm024a"><P><B>Code [perm024a]</B><P>
The indicated file has the setgid (group) bit set, but it should not
have it. This should be changed by using 'chmod g-s file' where 'file'
is the indicated file. The system should be checked for signs of
intrusion.
<PRE>










</PRE><HR>
<A NAME="perm025w"><P><B>Code [perm025w]</B><P>
If the 'arp' program is 'setgid', it can be used to read files that a user
normally should not be able to read. On many systems, this includes
/dev/kmem and /dev/mem. Turning the 'setgid' bit off will result in the
loss of 'arp -a' functionality for a normal user account. (On SunOS 5.x
systems, even this functionality isn't lost... there is no reason for
'arp' to be setgid). This is a minor loss of functionality.
<PRE>










</PRE><HR>
<A NAME="perm26f"><P><B>Code [perm26f]</B><P>
The file '/etc/login.access' provides finer control over user
access, it can be modified to allow or disallow remote access
to privileged accounts. If this file is writable by non-root
users, then unauthorized access or privileges may be obtained.
<PRE>










</PRE><HR>
<A NAME="perm27f"><P><B>Code [perm27f]</B><P>
The file '/etc/login.conf' is used by default on some BSD systems,
it can be used to set up user environment and to set policy and
accounting restrictions. Since this file provides control over user
access, if this file is writable by non-root
users, then unauthorized access or privileges may be obtained.
<PRE>










</PRE><HR>
<A NAME="perm28f"><P><B>Code [perm28f]</B><P>
The file '/etc/login.defs' is used by default on some Linux systems,
it can be used to set up user environment and to set policy and
accounting restrictions (such as password aging), as it defines
configuration control definitions for the login package.
Since this file provides control over user access, if this file
is writable by non-root users, then unauthorized access or privileges
may be obtained.
<PRE>










</PRE><HR>
<A NAME="perm29f"><P><B>Code [perm29f]</B><P>
The configuration files for PAM (Pluggable Authentication Modules)
are used by default on many Unix systems, it can be used to set up
the environment for some services and defined the policy for its
access. Since this file provides control over user access, if this file
is writable by non-root users, then unauthorized access or privileges
may be obtained.
<P>
More information about PAM is available from:
http://www.kernel.org/pub/linux/libs/pam/
and
http://www.sun.com/solaris/pam/
<PRE>










</PRE><HR>
<A NAME="perm30f"><P><B>Code [perm30f]</B><P>
The configuration files (/etc/ttys, /etc/default/login, /etc/security
or /etc/securetty depending on the operating system) determines
access to users based on what consoles are they logged in.
Since this file provides control over user access, if this file
is writable by non-root users, then unauthorized access or privileges
may be obtained.