Red Hat Bugzilla – Bug 804103
nss-pam-ldapd returns empty netgroup when a nonexistent netgroup is requested
Last modified: 2013-06-03 13:15:16 EDT
Description of problem: When user requests a netgroup that does not exist, nss-pam-ldapd returns an empty netgroup. Version-Release number of selected component (if applicable): 0.7.5-15 How reproducible: always Steps to Reproduce: 1. getent netgroup -s ldap thereisnosuchnetgroup Actual results: thereisnosuchgroup (denoting an empty netgroup) Expected results: nothing should be returned Additional info: Glibc (and sssd, for that matter), work fine: getent netgroup -s files thereisnosuchnetgroup <blank>
This is a known issue that is rather difficult to address. It stems from the fact that the NSS interface for netgroups is a bit weird. The request to nslcd is also a bit different from the rest. The nslcd protocol currently cannot distinguish between an empty netgroup and a non-existing one. For this to be possible to the protocol needs to be changed. That being said I don't think there should be many practical differences between an empty netgroup and a non-existing one.
(In reply to comment #2) > This is a known issue that is rather difficult to address. It stems from the > fact that the NSS interface for netgroups is a bit weird. The request to nslcd > is also a bit different from the rest. > > The nslcd protocol currently cannot distinguish between an empty netgroup and a > non-existing one. For this to be possible to the protocol needs to be changed. > > That being said I don't think there should be many practical differences > between an empty netgroup and a non-existing one. Thank you for chiming in, Arthur. It sounds like a fix would be invasive, moreover this issue has only been found during testing, it hasn't been reported in production. I'd still prefer to keep this bugzilla open for tracking purposes.
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.
FYI: the required protocol change has been made in the 0.9.0 release because backwards-incompatible changes were required anyway. The setnetgrent() function should now return an error for non-existing netgroups. Note that 0.9.0 is a development release and not recommended for production.