From owner-freebsd-bugs  Tue Jun 13 14:40:02 1995
Return-Path: bugs-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id OAA18515
          for bugs-outgoing; Tue, 13 Jun 1995 14:40:02 -0700
Received: (from gnats@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id OAA18508
          ; Tue, 13 Jun 1995 14:40:01 -0700
Date: Tue, 13 Jun 1995 14:40:01 -0700
Message-Id: <199506132140.OAA18508@freefall.cdrom.com>
From: Bill Fenner <fenner@parc.xerox.com>
Reply-To: Bill Fenner <fenner@parc.xerox.com>
To: freebsd-bugs
Subject: bin/509: netgroup cycle detection is broken
In-Reply-To: Your message of Tue, 13 Jun 1995 14:40:20 PDT
	<199506132140.OAA08511@baobab.parc.xerox.com>
Sender: bugs-owner@FreeBSD.org
Precedence: bulk


>Number:         509
>Category:       bin
>Synopsis:       netgroup cycle detection is too "greedy"
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs (FreeBSD bugs mailing list)
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Jun 13 14:40:00 1995
>Originator:     Bill Fenner
>Organization:
Xerox PARC
>Release:        FreeBSD 2.0-BUILT-19950527 i386
>Environment:

	
	FreeBSD 2.0.5-ALPHA
	running NIS in existing, largely Sun environment

>Description:

	
	getnetgrent() claims that there is a loop in the netgroup
	parc-decsD.  The problem is actually that the netgroup
	sun-access02D contains parc-decsD twice:

% ypmatch sun-access02D netgroup
parc-abekasD    parc-irisD      parc-vaxsD      parc-decsD      parc-ibmsD     parc-ncdsD       parc-decsD      parc-annexD

	Since it has visited the node before, it decides that there
	is a cycle in parc-decsD.


>How-To-Repeat:

	
	Create a netgroups file similar to:

	foo bar bar
	bar (baz,-,MYDOMAIN)

	getnetgrent() will complain that there is a cycle in bar.


>Fix:
	
	
	Not clear.  It's clearly less than ideal to list the same subgroup
	twice in the same netgroup entry, but it's also clear that the problem
	is not that there is a cycle.  Might be fixing the error message,
	might be fixing the checks.

>Audit-Trail:
>Unformatted: