> No, because that would require MySQL to 'see' the plain text version
> of the password. For MySQL to do that, the proces would look something
> like:
> PASSWORD()ed password ---> plain text ---> MD5ed password
> The first link in that chain is mathematically impossible (even if you
> never saw the plain text password, it would have to get to that stage
> in order to be put through the MD5 algorithm).
Okay, that makes the situation very clear. I now understand that MySQL
can not manipulate encrypted passwords for the purpose of changing
encryption methods. While this is not very convenient for my current
circumstances, I do also understand that this is for security purposes,
and protects the user's privacy.
I will have to copy over the user data, inserting in some temporary
passwords, and then require the users to create their own afterwards.
Thank you for your explanation. I can now make a plan to go forward with
the merging of the user tables.
Dave