Hmm. Well, I disagree. But I'm not sure I can make my case. There is obviously some sort of disagreement over it being "wrong" to represent LOCAL group membership using a REMOTE source. I think it's 'wrong'. All directory experience I've had says it's wrong. The commercial products I've delt with say it's wrong.
I simply do not believe storing membership in a LOCAL group on a REMOTE server is proper. The REMOTE server should do nothing other than vouch for REMOTE memberships. Granting those REMOTE memberships LOCAL access should reside completely on the client machine. By that I mean, the REMOTE service should establish that I am a member of "Remote Desktop Users". Locally "Remote Desktop Users" should be granted permissions to play audio files. Well, this is how MS Active Directory works anyways, and I am quite fond of it. -- Simpler integration for "local device" permissions https://bugs.launchpad.net/bugs/10225 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
