Likewise open and Likewise Enterprise utilize the same authentication mechanism and group membership determination. The differences are primarily on the Windows side (specifically schema changes to Active Directory), though Likewise Enterprise does use additional daemons for the enforcement of GPO updates and data collection.
Dropping down into unprovisioned mode (which is what Likewise Open functions at) would provide no additional information, and prevent me from logging into the affected boxes as myself (since the UID reported would no longer match the UID owning my home directory). There is no doubt that using the Open version would cause the same results. I think the deeper question is what mechanism is being used to determine group membership prior to verifying access with DBUS/PolicyKit, and why it is not querying /etc/group or /etc/gshadow? I am beginning to suspect that the bug is actually in changes made to PolicyKit rather than Network Manager or dbus. Either way, this is a serious bug with dramatic consequences -- the inability to integrate with a non-local authentication method places an Operating System squarely into the consumer category rather than the Enterprise category. The security ramifications are also dramatic: to allow my users to access the wirless network, I had to change the default permissions to "allow ownership". -- Networkmanager does not allow nm-applet to start for a network authenticated user. https://bugs.launchpad.net/bugs/449801 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
