[12734] in bugtraq
Re: local users can panic linux kernel (was: SuSE syslogd
daemon@ATHENA.MIT.EDU (Darren Reed)
Fri Nov 26 02:57:23 1999
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <199911250326.OAA27844@cairo.anu.edu.au>
Date: Thu, 25 Nov 1999 14:26:31 +1100
Reply-To: Darren Reed <avalon@COOMBS.ANU.EDU.AU>
From: Darren Reed <avalon@COOMBS.ANU.EDU.AU>
X-To: saw@MSU.RU
To: BUGTRAQ@SECURITYFOCUS.COM
In-Reply-To: <19991124120544.B400@castle.nmd.msu.ru> from "Savochkin Andrey
Vladimirovich" at Nov 24, 1999 12:05:44 PM
In some mail from Savochkin Andrey Vladimirovich, sie said:
[...]
> > sockets in this environment leads to false beliefs about what happens
> > at the other end. The syslog-sec mailling list has been discussing some
>
> With stream socket I get absolutely correct information: if I get a
> communication error then my message isn't properly logged.
Well, it may be that thinking of TCP/UDP reliability in terms of Unix
domain sockets (stream/datagram) is not correct. If other comments are
correct, then short of network buffer problems, there's no discerable
difference in the reliability of either streams or datagrams.
Flooding kernel log buffers (in BSD unix at least) can be done if you
expend enough effort dedicated to the task.
Darren
