From owner-freebsd-bugs Thu Feb 12 16:34:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA09391 for freebsd-bugs-outgoing; Thu, 12 Feb 1998 16:34:01 -0800 (PST) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA09370; Thu, 12 Feb 1998 16:33:58 -0800 (PST) (envelope-from wpaul@FreeBSD.org) From: Bill Paul Received: (from wpaul@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id QAA25995; Thu, 12 Feb 1998 16:33:45 -0800 (PST) Date: Thu, 12 Feb 1998 16:33:45 -0800 (PST) Message-Id: <199802130033.QAA25995@freefall.freebsd.org> To: kmitch@cslab.vt.edu, wpaul@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG Subject: Re: bin/5610 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: getpwnam and getpwuid do not use the +@netgroup convention in /etc/passwd. State-Changed-From-To: open-closed State-Changed-By: wpaul State-Changed-When: Thu Feb 12 16:22:28 PST 1998 State-Changed-Why: The PR description implies that +@netgroup substitutions don't work _at all_, which is not true. They do work, however it seems there was a bug that caused them to not work correctly in some circumstances. If you had a user that was a member of only one netgroup, then there was a bug in the getnetgrent.c module that would prevent the membership from being evaluated correctly. This has been fixed (thanks to Dirk for the patch) in both the -current and 2.2.x branch. There is some question that this is the cause of the problem that prompted this PR, due to the fact that no example is provided that demonstrates the failure. Without explaining the exact circumstances where the netgroup substitution breaks, there's no way to reproduce or fix the problem. However, I strongly suspect that this bug is in fact the culprit here, so I'm going to close out the PR. If the problem persists, please submit a new PR that includes a set of sample passwd and netgroup data, or any other configuration information, that illustrate the failure you are seeing. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message