This file is indexed.

/usr/lib/tiger/html/cron.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
<HR><PRE>








</PRE><HR>
<CENTER><H2> Documents for cron</H2></CENTER>
<A NAME="cron001w"><P><B>Code [cron001w]</B><P>
The listed cron entry does not use a full pathname for the listed command
(or if a shell is specified, the name of the shell script). Full pathnames
should be used for cron entries.
<PRE>










</PRE><HR>
<A NAME="cron002"><P><B>Code [cron002]</B><P>
The listed cron entry uses an executable or file which is not owned
by the owner of the cron entry, and is also not owned by a system
account (root or bin, etc). For root cron entries, these are especially
dangerous. Note that the actual problem may be with a directory in
the path to the file, not the file itself.
<PRE>










</PRE><HR>
<A NAME="cron003"><P><B>Code [cron003]</B><P>
The listed cron entry uses a file or executable which has group write
permissions, world write permissions or both. This can allow the
system to be compromised. For root cron entries, this is especially
dangerous. Note that the actual problem may be with a directory in
the path to the file, not the file itself.
<PRE>










</PRE><HR>
<A NAME="cron004w"><P><B>Code [cron004w]</B><P>
There is no crontab for the superuser account this is not in itself
an error since many systems might ship without one and use other
methods (/etc/cron* files) to run programs as root. However, if there
is no method for root to run scripts some system checking scripts
(like tiger) might not get executed at all.
<PRE>










</PRE><HR>
<A NAME="cron005w"><P><B>Code [cron005w]</B><P>
Cron allows users to submit jobs for the system to do at a
particular, possibly recurring time. It can be very useful, but also
has a very real potential for abuse by either users or system crackers.
Users can be restricted to use cron by creating a /etc/cron.allow
(holding only system administrators) or a /etc/cron.deny file
(listing which users are not allowed access). Depending on the site
configuration if none exist either only root will be able to setup
cron tasks or all users will be permitted. In many systems the
default is to allow access to all users.
<PRE>










</PRE><HR>
<A NAME="cron006w"><P><B>Code [cron006w]</B><P>
Cron is not restricted to a given user. It is usually good to restrict
cron as much as possible since this system has a real potential by
abuse by either users or system crackers. Consider removing the user
from the allowed cron list if it is not strictly needed.
<PRE>










</PRE><HR>
<A NAME="cron007i"><P><B>Code [cron007i]</B><P>
Cron is restricted to a given user. This is usually good, since
restricting cron prevents this system from being
abused by either users or system crackers.