[ducasi]

Originally posted by Logician
If unix passwords is in MD5, insert them as they are. If they are in plain text while inserting into vb database MD5 them so you wont need to hack vbulletin in anyway..

Unfortunately, they are in unix "crypt" (DES) format for compatibility across unix platforms that can't use MD5 passwords. And, of course, to make it harder we don't have the plain-text passwords...

After converting the existing users, you also need to write a script that will update the vb user table whenever a new unix user added/deleted from the system or whenever an existing user's unix password is changed (by Admin or by himself).

I plan to run a nightly script to do this as the password file is auto-updated on a nightly basis anyway...

And this approach is what I was already suggesting: Dont touch vb and adapt your other tools to work with vb's existing system. It seems that what you planned is exactly this.. IMO sound design..

I'm trying my best, but I still think I'll need to make vb use crypt-style passwords rather than md5...