Scott Haneda <[EMAIL PROTECTED]> wrote on 12/16/2005 08:46:29 PM:
> I need to do this just once...
>
> I have table zip_codes and table hardiness_zones
> In this case, the key will be the actual zip codes.
>
> hardiness_zones has two fields, zone_start and zone_end, these are all
empty
> in the
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
Dave wrote:
[snip]
I believe I will need to use the new password hashing algorithm, because
using the old one would require me to reconfigure the PHP code for the
forum, which would be a level of complexity beyond my capabilities.
So I now understand that I can not decrypt the passwords into
It did change between MySQL 3.2 and 4.1. You need the old-passwords
configuration directive, it is in the MySQL manual at dev.mysql.com.
Thank you. I believe the old-passwords configuration has already been
set by my web host.
You can't decrypt the password fields. That's the point of *one
Dave wrote:
[snip]
The current members tables uses the default PASSWORD encryption built
into MySQL. Although my current MySQL version is 4.1.3, I believe this
is the same password encryption that was used in MySQL 3.2. The user
data was created in an earlier version of MySQL, and later the
