Date: Wed, 6 Jan 1999 14:04:15 +0300 From: Vadim Kolontsov <vadim@tversu.ru> To: Darren Reed <avalon@coombs.anu.edu.au> Cc: freebsd-security@FreeBSD.ORG Subject: Re: kernel/syslogd hack Message-ID: <19990106140415.B14924@tversu.ru> In-Reply-To: <199901061044.VAA24694@cheops.anu.edu.au>; from Darren Reed on Wed, Jan 06, 1999 at 09:44:37PM %2B1100 References: <19990106132848.A14928@tversu.ru> <199901061044.VAA24694@cheops.anu.edu.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Wed, Jan 06, 1999 at 09:44:37PM +1100, Darren Reed wrote: > > > # mkdir /var/run/log.d > > > # chmod 700 /var/run/log.d > > > # ln -s /var/run/log.d/log /var/run/log > > > # syslogd -p /var/run/log/log > > > > Sorry, I didn't understand you. In which cases would it help? > > The above stops non-root from sending syslog messages, locally. I understand it, but I didn't understand in which *real* cases it can be useful? I can create "log" group and put all syslog()ing programs into it.. but I still don't sure it's useful. Regards, V. -- Vadim Kolontsov Tver Internet Center NOC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990106140415.B14924>