nslcd complains about / in groupnames
Bug #841660 reported by
Klavs Klavsen
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nss-pam-ldapd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
hosts using nslcd (and nss-ldapd) complains about group names with / in them:
nslcd[13021]: [3693ee] group entry cn=mount_
"mount_test/prod"
There's no such problem with nscd/nss-ldap. I haven't been able to find any dokumentation what is actually "officially supported" - but there was no problem creating these groups in openldap - and It's usually pretty good at vetting what it allows - so it seems it is an allowed group name.
I was hoping you could fix the "isvalidname" or whatever function is used to check group names - to allow /.
affects: | nss-ldapd (Ubuntu) → nss-pam-ldapd (Ubuntu) |
To post a comment you must log in.
nss-pam-ldapd has reasonably strict checking of user and group names to avoid problematic users existing by accident on the system. Version 0.8.2 introduces the validnames option that allows you to set a regular expression that will be used to filter valid names.
Note that nslcd is completely separate from nscd. libnss-ldapd requires nslcd and recommends nscd to ease the load on the LDAP server. libnss-ldap doesn't use nslcd and also recommends nscd for the same reason.