From owner-freebsd-security Sun Jun 6 22: 4:28 1999 Delivered-To: freebsd-security@freebsd.org Received: from jason.argos.org (a1-3b169.neo.rr.com [24.93.181.169]) by hub.freebsd.org (Postfix) with ESMTP id 1FEDC15529 for ; Sun, 6 Jun 1999 22:04:21 -0700 (PDT) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id BAA04329 for ; Mon, 7 Jun 1999 01:09:50 -0400 Date: Mon, 7 Jun 1999 01:09:50 -0400 (EDT) From: Mike Nowlin To: freebsd-security@FreeBSD.ORG Subject: Re: NIS strangeness In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Basically, if "root" is who's calling getpwnam(), the NIS lookup fails. > If any other user calls getpwnam(), it works. Example: > Here's an interesting bit of information: Running tcpdump with the "-x" option and decoding the hex bytes off the network, the NIS server IS sending back the correct line from master.passwd.byname in the 4th packet in the transaction when root calls getpwnam(). For some reason, it never seems to get back to the user program that called it, though. Ho, hum..... Time to go digging through libc's source.... :) --Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message