NineChime forum

I'm trying to rebuild a board that suffered cataclysmic problems (long story, suffice to say the DB is all that remains, but I MAY be able to lay my hands on the pictures from a former user).

I'm rebuilding it on my own server, so I have complete control of the environment. (NOTE: FIXED SEE BELOW)

I have set up 1.3.13, and it didn't give any complaints about the database.  It updated my 1.2 database and didn't throw any errors. The board can see all the users, and I can run a query from MYSQL on the userlist and nothing looks out of place.  It will not allow me to log in, though.  My suspicion is that something might have ended up out of synch because the installer tried to set up the owner as a user that already existed (me, in a previous incarnation), though it didn't throw an error that I can find.  WP is accessing the database, because I can see all the information that is available to an unregistered user, such as pictitles, comments, other users, etc, so it's not a question of DB access.

I tried blanking the password on my owner username in the database, but it still would not allow me to log in (I restored the hash that was there after I tried that).  I've tried creating a fake user, but it balks, claiming the Email can't be sent (and the fake user I'm setting up doesn't show up in the memberlist).  Checking php.ini, the mail settings seem to be correct (sendmail is where php.ini expects it to be).  I can telnet to port 25 and that works, so even though my sendmail isn't talking to the outside world, PHP shouldn't know that. (another PHP script I wrote for a local copy of my homepage happily sends the Email, even though Sendmail is probably suffering sensory deprivation fits in the background)

The flags in my username are GDMIUX (no "P") and I deleted the ninechime cookies from my list.  So.... Something is fubar.  Possibly the hash belongs to a different type?   Based on the length of the hash, I'm guessing standard DES.  Looks like from the code, you're not using automatic salt, so this may never work.  I have no idea what the salt from the old board was.

HA!  While I was composing this, I wrote a little script for generating a replacement password hash based on known salt (I think the old boards used automatic salt, because it's a number), and the hash I generated worked when subbed into the owner password.

Just put this script in a webpage by itself (I called it "crypt.php") and visit it.  DELETE IT AFTERWARDS, because this is your password in clear text!

<?php
if (CRYPT_STD_DES == 1) {
    echo 'Standard DES: ' . crypt('$yourpassword', '$yoursalt_from_config.php') . "\n";
}
?>

Copy the hash it generates and update the DB with it:
UPDATE op_oekaki SET usrpass='generated_hash' WHERE usrname="ownername";
(of course "op_oekaki" table would be different if you picked a different prefix)

After doing that, I can log in.

I suspect this means that all my users will have to request new passwords, because their old ones won't work, but I'll jump that shark when I get the page uploaded to an ISP.  I could try to look through all your release notes and find out when you went from automatic to pre-selected salt, but I'm lazy. :-)

Hope this helps someone who's got an old board backup they're having trouble mounting.