Ronnie Redd wrote: > OK, > (Please note the corrected path here - /etc/pam.d/vmware-authd instead of > /etc/pam.dvmware-authd) > > I went for it and I too confirm that the below fixes it on AMD64 Gutsy: > > replace the pam configuration in /etc/pam.d/vmware-authd to read: > > auth sufficient /usr/lib/vmware-server/lib/libpam.so.0/security/pam_unix.so > shadow nullok > auth required > /usr/lib/vmware-server/lib/libpam.so.0/security/pam_unix_auth.so shadow nullok > account sufficient /usr/lib/vmware-server/lib/libpam.so.0/security/pam_unix.so > account required > /usr/lib/vmware-server/lib/libpam.so.0/security/pam_unix_acct.so > > #%PAM-1.0 > @include common-auth > @include common-account > > I guess the point is: vmware does something special with their Pam modules which prevents the standard ones from being used. Perhaps this is the bug that should be noted, namely, why is vmware doing something special?
Yes, the above certainly fixes the problem. It should be noted that older versions of the package did the above which is how I figured out how to fix the problem. -- vmware server will not connect remotely https://bugs.launchpad.net/bugs/112937 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
