Hello Paul, Thursday, March 3, 2005, 10:03:39 AM, you wrote:
PJS> IIRC, the digest version of md5 uses a salt string very much like crypt does. So PJS> if your hash looks like $xxxx$xxxxxxxxxxx$ you're dealing with a digest. PJS> Curtis Maurand wrote: >> I'm in the process of writing a script that converts Linux passwd/shadow >> file into dbmail-users. The passwords are encrypted, but I don't know the >> difference between md5-hash-raw and md5-digest-raw. does anyone here >> know? >> >> Curtis >> >> _______________________________________________ >> Dbmail mailing list >> [email protected] >> https://mailman.fastxs.nl/mailman/listinfo/dbmail >> Sorry, but I should say you are wrong. Linux and UNIX both use MD5 hash in the shadow file. This is what is used for password encryption. In fact, it is a hash, because it does not store the password. Every time one tries to login, the password that he enters is hashed with the salt from his stored MD5 hash. This way you will get the same MD5 hash again, only if you entered the correct password. So, regarding dbmail - dbmail has native MD5 hash support (thanks to me at some degree I hope) and also for MD5 digests. Since digest are originally used for file checksums, I advise all to use MD5 hashes. Curtis, your case is quite simple. I have already done it, and it was in the days dbmail had no support for MD5. What you need to do is take the shadow file and replace all ':' between the user and the hash with ';' or ',' for example. Then you could easily import the data into MySQL (you may use PHPMyAdmin for that). I'm not certain, but you may try to do it even without changing the ':' :) It will be your separator. The last thing is to put 'md5' as encryption_type in the dbmail users table. That's it. Hope that you have compiled (if manually) dbmail with the right crypt library, that is with -lcrypt (man crypt, section GNU EXTENSION). Best regards, Bobby [EMAIL PROTECTED]
