-
-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
strong password not being hashed correctly #4004
Comments
Confirmed. This happens because
Doing more testing to see how we can fix this Edit: @CaMer0n Would it be safe to exempt the password field from this filter routine? And process it exactly as entered? Same as with the 'ue' fields? Later on, the password will get hashed anyway. E.g. $ueVals = $_POST['ue'];
$passtemp1 = $_POST['password1'];
$passtemp2 = $_POST['password2'];
$_POST = e107::getParser()->filter($_POST);
$_POST['ue'] = $ueVals;
$_POST['password1'] = $passtemp1;
$_POST['password2'] = $passtemp2; Optionally we can also make use of |
This has now been fixed. It is not the cleanest method, and perhaps we need to adjust the e107::getParser()->filter() method to include the FILTER_FLAG_NO_ENCODE_QUOTES flag but for now this works. |
Issue: special characters in password break the hash
Steps to reproduce:
I installed the latest released version (e107 V2.2.1) and during setup I used a randomly generated strong password for the Administrator account:
H?r}Fz^bT4N"`DU8
Upon completing the installation, I was unable to log in to the admin account. (Wrong password)
I changed the password in mysql via the cli to the md5 hash of "changeme" (4cb9c8a8048fd02294477fcb1a41191a) and was able to log into the admin account with this password.
I immediatly changed the password back to the originally intended strong password H?r}Fz^bT4N"`DU8 and again was not able to log back in and had to manually reset it back again to "changeme".
The text was updated successfully, but these errors were encountered: