Well, guys, I met this problem today, and finally I resolved this. if you take a look on /etc/shadow, you will see the shadow password is too long than the normal case,
============= shadow =================== test1:$1$yzJSeIFS$FmhQgNYYD/BhapUkes0ME1:14438:0:99999:7::: test2:$6$CJOO9de/$ddz3ZkubIO8mGacvRkhMUX3cz0n2u0I4dLZMxila8iBsXN8q2QKYnx0X1dY0CGDsTDw9xgDcWbf0ilfd/1WX01:14438:0:99999:7::: ============================ this case, test1 is using md5, and test2 using sha512, vmware doesn't support sha512. Turn back, try to look /etc/pam.d/common-password: there should be a line: password [success=1 default=ignore] pam_unix.so obscure sha512 that caused the problem, the pam_unix.so in vmware directory can only support md5 value, don't support sha512. what you need to do is change it back to: password requisite pam_unix.so nullok obscure md5 then using passwd to change user password, it should be ok now. I don't know which package update common-password file, maybe caused by "pam-auth-update" in libpam-runtime what a stupid design. -- amd64 + vmware 1.0.9 vmware-authd broken https://bugs.launchpad.net/bugs/363272 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
