From owner-freebsd-bugs  Thu Mar 16 09:20:01 1995
Return-Path: bugs-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA13383 for bugs-outgoing; Thu, 16 Mar 1995 09:20:01 -0800
Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA13376; Thu, 16 Mar 1995 09:20:01 -0800
Date: Thu, 16 Mar 1995 09:20:01 -0800
Message-Id: <199503161720.JAA13376@freefall.cdrom.com>
From: roottcsh@alano.diatel.upm.es
Reply-To: roottcsh@alano.diatel.upm.es
To: freebsd-bugs
Subject: misc/244: reading groups from YP causes core dumps in a client machine
In-Reply-To: Your message of Thu, 16 Mar 1995 18:13:37 +0100
	<199503161713.SAA01786@alano.diatel.upm.es>
Sender: bugs-owner@FreeBSD.org
Precedence: bulk


>Number:         244
>Category:       misc
>Synopsis:       reading groups from YP causes core dumps in a client machine
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs (FreeBSD bugs mailing list)
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Mar 16 09:20:00 1995
>Originator:     Operator
>Organization:
>Release:        FreeBSD 2.0-RELEASE i386
>Environment:
YP/NIS is served by a machine running SunOS 4.1.1.
DES encryption is installed in the FreeBSD machine (from skeleton.mikom.csir.co.za).
	

>Description:
If you enable group sharing under YP (that is, you add the special "+" group
entry to /etc/group), any process that attempts to get the
list of group ids of a user, dies with a core dump.

Note: enabling YP for user ids seems to work fine.
	

>How-To-Repeat:
After starting NIS (make /var/yp ; ypbind), append the following to /etc/group:
+:::

Now, attempt to login. It will core dump when starting up your session.
Or execute "id someone". It will core dump.
Or wait until cron executes atrun. atrun will core dump.
	

>Fix:
Not known.

The only thing I've done is get a stack dump of a process that dies because of
this:

The command executed is "id jmrueda". gdb reports:

Program received signal SIGSEGV (11), Segmentation fault
0x8055870 in strtol.so ()
(gdb) bt
#0  0x8055870 in strtol.so ()
#1  0x80500cc in atoi.so ()
#2  0x802f712 in _gr_breakout_yp ()
#3  0x802f975 in _nextypgroup ()
#4  0x802f208 in getgrent ()
#5  0x802f9e5 in getgrouplist.so ()
#6  0x1daa in user (pw=0x807803c) at id.c:242
#7  0x18fb in main (argc=1, argv=0xefbfde0c) at id.c:142
	

>Audit-Trail:
>Unformatted:


: