During the process of adding a new user from the admin page,
YumPasswordValidator.php is called multiple times with different $objects.
The first call is with the YumUserChangePassword object and contacts the clear
text password.
Subsequent calls contain the encrypted password. During these subsequent
calls, the various password requirements, such as the max length will be tested
against encrypted values, not clear text values. On my systems, the encrypted
pw has a length of 32 while the clear-text pw has a length of 8. Using a
maxLen pw value of 12 will cause the legitimate pw (with a length of 8 to fail
the requirements test).
A workaround (probably not the correct fix is to add the following to the top
of the YumPasswordValidator.php program:
$class = get_class($object);
if ($class != 'YumUserChangePassword') {
return;
}
Original issue reported on code.google.com by N.Brandi...@gmail.com on 21 Sep 2010 at 5:32
Original issue reported on code.google.com by
N.Brandi...@gmail.com
on 21 Sep 2010 at 5:32