Serendipity Forums

Hiya how are you? im having problems login in to my admin suite, iv forgot my password

im currently on version: Serendipity 1.5.5 and PHP 5.2.12

iv loged in to phpmyadmin and edited the

serendipity_authors table that has my username and password details,

iv selected edit and changed the password and selected md5 on the drop down table and i didnt edit anything else, and i selected save.
i can see the hashtype colum is there and is currently on "1"

I then tried to login, but with no success, i keep getting this message: You appear to have entered an invalid username or password

i downloaded a fresh copy of serendipity and uploaded it and edited the serendipity_config_local.inc file and changed the installed version from 1.5.5 to 1.4 to force an upgrade which went file although i got a duplicate error message for hashtype which was expected.

i dont know what else to try, i just cant remeber my password please help


can you install the password recovery plugin without having to login to the admin suite? so that i can reset my password?

i look foward to hearing from you

Thankyou

i hope i dont have to lose my s9y blog i have been using this blog for 8 years.

i look foward to your assistance

Try changing the hashtype to something other than 1....

Perhaps this post will help you: http://board.s9y.org/viewtopic.php?f=3&t=17697

Hi don thankyou for your reply, iv just tried that with a different number other than 1 still cant seem to login.

hashtype 1 is ok and should not be changed.

Recent s9y versions >1.5 no longer use MD5 hashing, but sha1 with a salted hash.
Please read about fix-YOUR-login and test-MAIN-users scripts in case of upgrades here:

fixlogin.php: http://board.s9y.org/viewtopic.php?f=1& ... #p10425053

or here
testusers.php: http://board.s9y.org/viewtopic.php?f=3& ... #p10424763

I merely mentioned setting it to something other than one due to this quote on the other thread by Garvin:

S9y has a fallback mechanism, when the hashtype is "non-1", it will use md5 login, then properly store the new sha1 value and switch hashtype to 1. So in your case, you should've repaired that mechanism properly.

Regardless, perhaps the fixlogin.php suggestion will do the trick.