-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Password hashing has long been among our top support issues.
Once upon a time, Rails came bundled ruby-mysql 0.2.4 [1]
It doesn''t support the new MySQL 4.1 client protocol or new-style
password hashing, so in January 2005 Matt Mower wrote the mysql411
shim, activated if the server version >= 4.1.1, which adds support
for these new features but breaks old-style password hashing.
This is included with Rails; otherwise, we have no out-of-the-box
support for the stable MySQL release. Unforunately, it means that
users who are migrating from 4.0 or earlier must deal with the
password hashing headache.
The answers are:
1. gem install mysql. This installs mysql-ruby 2.7 C driver [2]
which is faster and supports MySQL 4.1 and later. However, there is
no Windows binary gem available.
2. Upgrade the database to new-style password hashing [3]. Some
users on shared hosts cannot do this (apparently) and it is an
annoying step to perform.
3. Use an empty password. Then hashing is not an issue.
These are poor answers. Solutions:
- Improve MySQL 4.1+ support in ruby-mysql [1]. Merge the nice,
clean patch by ?? ? <akuroda at gmail.com> [4] with ruby-mysql
0.2.6 and include it with Rails.
- gem install mysql. We need to package the compiled mysql-ruby
2.7 bindings [2] as a binary gem for Windows.
This is an open call for anyone to take a crack at the problem.
Either solution would make a lot of people very grateful.
Best,
jeremy
[1] http://tmtm.org/en/ruby/mysql/
[2] http://tmtm.org/en/mysql/ruby/
[3] http://dev.mysql.com/doc/refman/5.0/en/old-client.html
[4] http://tmtm.org/ruby/mysql/ruby_mysql4.patch
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (Darwin)
iD8DBQFDcHHMAQHALep9HFYRArhGAKCdsfT/0GgET64dVq1pweBS72fydwCgztM3
CjaTlhLwZrDtYP4jow2cjI0=8i2V
-----END PGP SIGNATURE-----