Nmap Security Scanner
*Intro
*Ref Guide
*Install Guide
*Download
*Changelog
*Book
*Docs
Security Lists
*Nmap Hackers
*Nmap Dev
*Bugtraq
*Full Disclosure
*Pen Test
*Basics
*More
Security Tools
*Pass crackers
*Sniffers
*Vuln Scanners
*Web scanners
*Wireless
*Exploitation
*Packet crafters
*More
Site News
Site Search:
Exploit World
Advertising
About/Contact
Credits
Sponsors:
edgeos



Vulnerability Development: Re: slackware permissions

Re: slackware permissions

From: Sam Vaughan <yamaneko_at_centurytel.net>
Date: Sat, 4 Aug 2001 00:55:32 -0700 (PDT)

Having /var/log/cron set to 600 will not affect user's cron jobs.

Dillon cron's logging is either done through syslog or from the output of
crond. On the other hand, I don't think logging is going to /var/log/cron
by default. It just gets created upon start up.

from the rc.d script that starts cron

# Start crond (Dillon's crond):
# If you want cron to actually log activity to /var/adm/cron, then change
# -l10 to -l8 to increase the logging level.
/usr/sbin/crond -l10 >>/var/adm/cron 2>&1

(note in slackware /var/adm is a link to /var/log)

Hope this helps,
Sam

On Fri, 3 Aug 2001, denis wrote:

>
> If it's 600, then how are user's cron jobs going to be run??
>
> Denis
>
> On Fri, 3 Aug 2001, Sam Vaughan wrote:
>
> >
> > On my Slackware 8.0 box it is.
> >
> > $ ls -l /var/log/cron
> > -rw-rw-rw- 1 root root 0 Jul 22 21:50 /var/log/cron
> >
> > this should be chmod 600
> >
> > Sam
> >
> >
> >
> > On Fri, 3 Aug 2001, Tony Lambiris wrote:
> >
> > > Can anyone else confirm or deny that /var/log/cron has perms 666 in
> > > slackware 8.0? I checked on my desktop, and two laptops, and they all
> > > had 666 as the perms.
> > >
> > > Thanks.
> > >
> >
>
>
Received on Aug 04 2001

[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]
edgeos