From owner-freebsd-security Thu Jul 8 23:49:27 1999 Delivered-To: freebsd-security@freebsd.org Received: from buddy.sovlink.ru (buddy.sovlink.ru [194.186.12.9]) by hub.freebsd.org (Postfix) with ESMTP id AD8DE14CE9 for ; Thu, 8 Jul 1999 23:49:21 -0700 (PDT) (envelope-from alla@sovlink.ru) Received: from sovlink.ru (punk.sovlink.ru [194.186.12.133]) by buddy.sovlink.ru (8.9.1/8.9.1) with ESMTP id LAA03791 for ; Fri, 9 Jul 1999 11:00:46 +0400 (MSD) Message-ID: <37859B74.7528C158@sovlink.ru> Date: Fri, 09 Jul 1999 10:49:24 +0400 From: Alla Bezroutchko X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: FreeBSD Security Subject: Syslog alternatives? Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is not exactly FreeBSD security question. More like general Unix security. Hope it is not completely off topic. I was looking at several syslogd alternatives (BTW, I don't think I have a complete list, can you suggest something?) and found out that I don't understand what is wrong with traditional syslogd from security standpoint. Could someone explain me or point me to some resources that explain why syslogd is bad? -- Alla Bezroutchko Sovlink LLC Systems Administrator Moscow, Russia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message