I've just notified VMware of the issue, they'll get some engineering to take a look and provide either a clarification or KB
=========================================================================
William Lam
VMware vExpert 2009,2010
VMware scripts and resources at:
Getting Started with the vMA (tips/tricks)
Getting Started with the vSphere SDK for Perl
VMware Code Central - Scripts/Sample code for Developers and Administrators
If you find this information useful, please award points for "correct" or "helpful".
Was just about to do the same.
I wonder what affect there might be with AD.
I have not dove in too deep on the issue yet, but I sure VMware is using some kind of LUM (Linux Enable User) software with AD to function much like Edir LUM for SUSE form Novell. There was a lot of issues with LUM and PAM on Novell's 1st and even 2nd go around, I am hoping that VMware has better luck.
The way it is setup sounds to me like the feature is just pulling in LDAP information from AD.
I can confirm the issue as well - I performed an upgrade from the RC build
Maish - VCP - vExpert 2010
VMware Communities User Moderator
Virtualization Architect & Systems Administrator
I can confirm the issue as well - I performed an upgrade from the RC build <br>Maish - VCP - vExpert 2010
Did you test this issue before you upgraded from GA?
No I did not
Maish - VCP - vExpert 2010
VMware Communities User Moderator
Virtualization Architect & Systems Administrator
I installed a copy of build 260247 in Workstation with a 10 digit password. I can reproduce the same results.
As long as the first 8 characters are correct I can enter only the 8 or anything after the 8 and it will accept it and log me in.
VMware VCP - Consider awarding points for "helpful" and/or "correct" answers.
I confirm the issue with ESXi4.1.0 fresh or upgrade from ESXi4.0.
The workaround would be:
1- vi /etc/pam.d/system-auth and change this line accordingly:
password sufficient /lib/security/$ISA/pam_unix.so use_authtok nullok md5 shadow
save and exit the file with :wq!
2- change your password in DCUI,
3- verify that it has encrypted your root’s password using MD5 algorithm: cat /etc/shadow <- If root’s password hash starts with a ‘$1$‘ then MD5 algorithm was used.
N.B. Don't do that in a production environment!
Read more at deinoscloud.wordpress.com
I wish I was a virtual machine ![]()
thanks for sharing the tips in how to make it secure, however, may i know why you' suggesting "Don't do that in a production environment" ?
In general when you access tech support mode you should do under the guidance of VMware support. For this issue the "supported" change is documented here - http://kb.vmware.com/kb/1024500.
Dave
VMware Communities User Moderator
Now available - vSphere Quick Start Guide
Do you have a system or PCI card working with VMDirectPath? Submit your specs to the Unofficial VMDirectPath HCL.
Patch was released today
New Patch released - VMSA-2010-0016
Maish
VMware Communities User Moderator