Strong opinions, weakly held

Moving Movable Type

I’m trying to get Movable Type up and running on a different server to test out some things (like the new beta), but I am running into another problem. I dumped my SQL database to disk and then loaded it into a new database, and now I can’t seem to log into the new installation. Any idea what’s up with that? Is the password encryption somehow tied to the host where Movable Type is installed?


  1. MySQL has changed their password hashing algorithms a couple of times, relatively recently. If you are changing MySQL versions, you could run into that problem. More info here: http://dev.mysql.com/doc/mysql/en/password-hashing.html

  2. It’s not a problem with the MySQL password (or doesn’t seem to be). Rather, my MySQL author password won’t work. I thought maybe they used the MySQL password hashing algorithm, but I did some testing and that turns out not to be the case.

  3. This is purely a guess, based on observations I have made with other software (wince I never used MT): Could it be that the domain/path settings you have in the db might be messing up your login – if it tries to set/check for the wrong cookies, this might prevent you from logging in.

  4. I’ve figured out what’s causing the problem, though not how to solve it. Basically, the Perl crypt function (which is just a passthrough to the system level crypt function) returns different results on the pair.com host (running FreeBSD 4.8) and the other host (running FreeBSD 5.4). So when Movable Type compares the crypted value in the database to the one generated from the password the user enters, the results aren’t the same and the login fails.

    Obviously I could reset the password in the database as encrypted on the new system, but I’m quite puzzled as to why the results of crypt are different in the first place.

  5. Rafe, if you had your password hint and email set in your author profile, just use the Forgot Password utility. If not, you can set both fields via a DB web interface. This would be easier than crypting a new password by hand.

    I’ve never heard of such a problem as yours before. Would you be so kind as to file a bug on that? (See http://www.sixapart.com/movabletype/beta/2005/07/filing_bugs.html)


  6. Password problem fixed

    I fixed the password problem that I mentioined yesterday. It actually turned out to require some detective work. To test my Movable Type installation on a new server, I backed up my database and loaded it on the new MySQL…

Comments are closed.

© 2016 rc3.org

Theme by Anders NorenUp ↑