[12731] in bugtraq

home help back first fref pref prev next nref lref last post

Re: local users can panic linux kernel (was: SuSE syslogdadvisory)

daemon@ATHENA.MIT.EDU (der Mouse)
Fri Nov 26 01:46:34 1999

Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Message-Id:  <199911241753.MAA08769@Twig.Rodents.Montreal.QC.CA>
Date:         Wed, 24 Nov 1999 12:53:28 -0500
Reply-To: der Mouse <mouse@RODENTS.MONTREAL.QC.CA>
From: der Mouse <mouse@RODENTS.MONTREAL.QC.CA>
X-To:         BUGTRAQ@SECURITYFOCUS.COM
To: BUGTRAQ@SECURITYFOCUS.COM

> As long as syslog uses a connected socket (which it does), and
> doesn't flag MSG_NOWAIT (which it doesn't), there isn't anything in
> the kernel source that looks like the code will fail under
> cpu/memory/whatever contention.

That's *heavily* OS-dependent.  Not all implementations of AF_LOCAL
sockets work the same.

> Just because UDP datagrams are unreliable that doesn't mean that UNIX
> datagrams are too.

True.  But don't forget either that just because one implementation of
AF_LOCAL actually is reliable doesn't mean that they all are.  (Though
if AF_LOCAL sockets are reliable, they should be SOCK_RDM rather than
SOCK_DGRAM, I think.)

					der Mouse

			       mouse@rodents.montreal.qc.ca
		     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B

home help back first fref pref prev next nref lref last post