![]() |
Same username+password as live but login with it locally.
I am staging for an upgrade from 4.1x to 4.2.2.
I pull down db+code, run upgrade, go to login as admin and it rejects credentials. I compare live/local password+salt for userid=1 and they are the same. I run the following using the ACTUAL admin password: Code:
UPDATE `user` Is the updated codebase using a different hashing method being used? What's going on? Thank You :) |
Quote:
That is strange, but the hashing algorithm hasn't changed, and if it had your update wouldn't have fixed the problem. |
As a precaution, I suppose I can force users to reset their password after this upgrade. The site was hacked a little while back. I slapped on a temporary bandage. So forcing users to reset their password with this upgrade wouldn't be a bad thing.
|
That sounds like a good idea, will ensure you are secure then. :)
|
I wonder if it could be a difference in character sets between databases? Forcing users to change password might not be a bad idea, but if you want to figure out why you're having a problem, maybe you could put some test code in includes/functions_login.php, in function verify_authentication, to see what's happening.
|
Good catch!
Live collation: utf8_unicode_ci I created local as: utf8_general_ci Thank you!! :) --------------- Added [DATE]1391471124[/DATE] at [TIME]1391471124[/TIME] --------------- Since we are on the subject, I forget why it was ever set to utf8_unicode_ci. The site is an English language site. Is there a problem with leaving it as utf8_unicode_ci? |
Quote:
|
All times are GMT. The time now is 06:48 PM. |
Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|