From owner-freebsd-current Wed Oct 2 7:28:32 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 625A837B404; Wed, 2 Oct 2002 07:28:29 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88D9543E6A; Wed, 2 Oct 2002 07:28:28 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.4/8.12.4) with SMTP id g92ES1Oo046106; Wed, 2 Oct 2002 10:28:01 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Wed, 2 Oct 2002 10:28:01 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Maxim Konovalov Cc: current@FreeBSD.org Subject: Re: NIS broken by pw_scan.c commits? In-Reply-To: <20021002110703.W72260-100000@news1.macomnet.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 2 Oct 2002, Maxim Konovalov wrote: > Yes, it is my bug, fixed in rev. 1.23, sorry for inconvenience. No problem -- sorry for getting a bit snippy. I was just a bit surprised and couldn't imagine at first what I had broken in my password file :-). > By the way, there is still an issue: pw_scan() allows an empty GID in > non-NIS entries too. Any objections to a patch below? It looks to me like this is a reasonable approach, but if for some reason it doesn't work out, I'll be sure to whine when it hits my office machines. :-) Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message