Date: Wed, 18 Oct 1995 13:36:50 -0700 From: scotte@center.uscs.com To: FreeBSD-gnats-submit@freebsd.org Subject: bin/786: Problem with NIS and large group maps Message-ID: <199510182036.NAA01085@queasy.center.uscs.com> Resent-Message-ID: <199510182040.NAA20875@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 786 >Category: bin >Synopsis: Problem with NIS and large group maps >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Oct 18 13:40:02 PDT 1995 >Last-Modified: >Originator: L. Scott Emmons >Organization: __________________________________________________________________________ L. Scott Emmons | CableData R&D Center - El Dorado Hills, CA, USA (916)939-6088 | >> Standard disclaimer applies. Views are my << scotte@center.uscs.com | >> own, not those of U.S. Computer Services. << >Release: FreeBSD 2.0-BUILT-19950603 i386 >Environment: FreeBSD 2.0.5 running as an NIS client. >Description: When the groups NIS map contains entries with very long lines the system becomes unstable as login, cron, and many other programs get segmentation faults attempting to read the groups file from NIS. My guess is that a strcpy() or the like is used without checking that no more bytes are copied than the size of the destination area. >How-To-Repeat: Create a group on an NIS server with a very, very long line. On the FreeBSD client, add the "+" magic cookie into the "/etc/groups" file. Now try to log into the system. In this case, the offending groups line is about 850 bytes long. >Fix: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199510182036.NAA01085>