public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wjones at fluke dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/15385] New: Results from "getent group" may be truncated with nss_db Date: Mon, 22 Apr 2013 22:11:00 -0000 [thread overview] Message-ID: <bug-15385-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=15385 Bug #: 15385 Summary: Results from "getent group" may be truncated with nss_db Product: glibc Version: 2.15 Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: unassigned@sourceware.org ReportedBy: wjones@fluke.com CC: drepper.fsp@gmail.com Classification: Unclassified The results from "getent group" may be truncated when using nss_db. This will happen when getgrent() encounters a group entry long enough to overflow the default 1024 byte buffer. getgrent() sets errno to ERANGE and returns NULL, but getent fails to check errno, and truncates the results at this point. Two things make me suspect that this failure is avoidable: 1. Requesting a specific long group entry will return it in full, e.g.: getent group myverylonggroup 2. Our local configuration in /etc/nsswitch.conf looks like this: group: files db Long entries in group.db will cause output from "getent group" to be truncated as described, but if I add a long entry to /etc/group, it will be output in full, along with all subsequent entries in group.db. It appears that that nss_files will grow the buffer as required, and then the expanded buffer is used by nss_db. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2013-04-22 22:11 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-22 22:11 wjones at fluke dot com [this message] 2013-04-22 22:12 ` [Bug libc/15385] " wjones at fluke dot com 2014-06-13 18:22 ` fweimer at redhat dot com 2015-04-08 20:19 ` kbonner at gmail dot com 2015-08-27 21:54 ` [Bug nss/15385] " jsm28 at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-15385-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).