Just because a process runs as root does not necessitate that it becomes a
security hazard.
Running as root is actually a special case recognized by fetchmail where it will
service remote pop accounts for all users and follow a mappings file to deliver
them locally.
Otherwise, you have dozens of daemons doing the same thing, but for different users.
On Mon, Dec 06, 1999 at 11:23:46AM -0600, Jeff Smelser wrote:
> On Sat, 4 Dec 1999, J. Scott Kasten wrote:
>
> > No need to CRON it. Config and run it as root and it daemonizes and serves
> > all local users that you profile.
> >
> > On Sat, Dec 04, 1999 at 10:54:30AM -0800, Stephen King wrote:
> > > I would imagine that fetchmail as a cron job would be the one for the job
> > > of getting the mail from multiple POPs to local users and maybe diald to
> > > connect the PPP when needed. Then have the network machines check for mail
> > > on the local machine that is running the aforementioned progs.
> > >
>
> Running as root is just another security hazard. It will run fine as a
> normal user. Why run as root? It will Daemon under a user.
>
> Jeff
--
J. Scott Kasten
jsk AT tetracon-eng DOT net
"That wasn't an attack. It was preemptive retaliation!"
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
