Date: 07 Jun 1999 17:29:11 +0200 From: Dag-Erling Smorgrav <des@flood.ping.uio.no> To: Mike Nowlin <mike@argos.org> Cc: Dag-Erling Smorgrav <des@flood.ping.uio.no>, John Baldwin <jobaldwi@vt.edu>, Wes Peters <wes@softweyr.com>, freebsd-security@FreeBSD.ORG Subject: Re: NIS strangeness Message-ID: <xzpso84kp14.fsf@flood.ping.uio.no> In-Reply-To: Mike Nowlin's message of "Mon, 7 Jun 1999 11:23:47 -0400 (EDT)" References: <Pine.LNX.4.05.9906071122550.4850-100000@jason.argos.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Mike Nowlin <mike@argos.org> writes: > > The test program you posted doesn't do *any* error-checking... which > > means that if getpwnam() fails, your program will happily try to > > dereference a null pointer, hence the SIGSEGV. > Shoulda put that disclaimer in -- that one was quick-and-dirty -- > normally, my programs aren't that badly done.. :) Yes. I was trying to point out that the SIGSEGV is not a manifestation of the bug itself, but a consequence of the lack of error checking. Anyway, I can't seem to reproduce this bug, and I suppose it would be too much to ask for a root shell on the affected machine :) DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no 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?xzpso84kp14.fsf>