Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 04 Jan 2019 21:33:38 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 234622] [libc] getgrent() issue with large NIS groups
Message-ID:  <bug-234622-227@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234622

            Bug ID: 234622
           Summary: [libc] getgrent() issue with large NIS groups
           Product: Base System
           Version: 11.2-RELEASE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: tcleamy@ucdavis.edu

Created attachment 200779
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D200779&action=
=3Dedit
Patch for 11.2

getgrent misses large NIS groups so the group list for those users is
incorrect.

To replicate simply make a large NIS group (500+ characters) and then run
groups on one of those users.  From one of my systems:
> ypmatch crc group
crc::499:ccctim,itsnoopy,rodd,jkperla,ncmolina,ajnichol,itlm003,itlm005,itl=
m011,itlm012,itlm019,itlm022,itlm023,itlm031,itlm032,itlm033,itlm034,itlm03=
5,itlm038,itlm039,itlm040,itlm041,itlm043,itlm045,itlm046,itlm049,itlm054,i=
tlm055,itlm057,itlm061,itlm064,itlm067,itlm068,itlm070,itlm071,itlm072,itlm=
076,itlm079,itlm080,itlm082,itlm084,itlm086,itlm087,itlm088,itlm089,itlm091=
,itlm092,itlm094,itlm095,itlm097,itlm098,itlm099,itlm100,itlm104,itlm107,it=
lm109,itlm111,itlm112,itlm113,itlm114,itlm123,itlm125,itlm126,itlm127,itlm1=
30,itlm134,itlm138,itlm140,itlm141,itlm145,itlm146,itlm147,itlm151,itlm167,=
itlm179,itlm196,itlm197

> groups ccctim
users lm hws projects office eyevocab roomres crcsuper

So while "ypmatch crc group" lists the entire group including ccctim, "grou=
ps
ccctim" doesn't list crc.

I've seen this issue on various releases of FreeBSD 9, 10 & 11.  I think it=
's
the same as 96840.  That bug report says fixed and closed, but I'm continui=
ng
to see the same issue.  I've been using that patch in 96840 to fix the bug =
each
release.  So can you double check to see if the issue was really fixed?

I've attached the latest patch for FreeBSD 11.2.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-234622-227>