** Description changed: Binary package hint: coreutils id 5.97 fails to report secondary groups depending on the case of the username. Example: If you have an Ubuntu domain member Samba server on a NT4/Win2k/Win2k3 network, the following occurs (from a posting in the Samba mailing list): -------------------------------------- With the "normal" setup (winbind use default domain = No): id DOMAINNAME\\username - shows all groups id DOMAINNAME\\USERNAME (or any permutation with a cap in the username) - only primary groups id username - returns "No such user" (normal) -------------------------------------- If I set "winbind use default domain = Yes" then: id DOMAINNAME\\username - only primary groups id DOMAINNAME\\USERNAME (or any permutation with a cap in the username) - only primary groups id Username - (or any permutation with a cap in the username) - only primary groups id username - shows all groups -------------------------------------- These are all valid examples that should all yield the same results containing all groups for the user. Some versions will also list, or not list secondary groups depending on whether or not the user issuing the id command as root. I have seen this behaviour in id 5.97, but not in 5.2.1 (pre-rewrite?). It seems to work fine for me in id 6.7, but I have seen a report of another user claiming that 6.7 also fails. - Why do we care?: Because it potentially sends server operators on wild - goose chases trying to debug Samba(winbind) when the fault actually is - with id. The id utility is one of the tools used to verify a new - winbind setup is functioning properly. I have seen several postings on - various newsgroups and lists over the last few years mentioning this - problem without the users realizing the problem may originate with a bug - in id. + This issue potentially sends server operators on wild goose chases + trying to debug Samba(winbind) when the fault actually is with id. The + id utility is one of the tools used to verify a new winbind setup is + functioning properly. I have seen several postings on various + newsgroups and lists over the last few years mentioning this problem + without the users realizing the problem may originate with a bug in id.
-- id fails to report secondary groups w/ samba https://launchpad.net/bugs/85384 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
