Date: Wed, 6 Jan 1999 13:28:48 +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: <19990106132848.A14928@tversu.ru> In-Reply-To: <199901060935.UAA24071@cheops.anu.edu.au>; from Darren Reed on Wed, Jan 06, 1999 at 08:35:23PM %2B1100 References: <19990106095543.B28727@tversu.ru> <199901060935.UAA24071@cheops.anu.edu.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, On Wed, Jan 06, 1999 at 08:35:23PM +1100, Darren Reed wrote: > nsyslogd (when it finally gets the hashing/encryption enabled) will provide > a constant flow. To it, the hashed and encrypted stream of data is just > another source, not a special thing which is handled differently. this is good news; I'd like to say "Thank you!" for all your work! > As far as /var/run/log goes, chown/chgrp/chmod are your friends or you > can make /var/run/log a symbolic link to a protected directory with which > you use the -p argument to place the log socket. e.g.: > # 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? 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?19990106132848.A14928>