MySQL connection security has been upgraded in MySQL version 4.1 and onwards (current release is 5.0). A quote from the MySQL relevant information page.
Currently if you develop a RunRev app that needs to connect with an existing MySQL database server that is version 4.1 or above, you will need to re-configure the server to use the old style, less secure passwords. The MySQL web article (above) states that the older client used by RunRev is less secure than the new client, even if you don't consider the password strength issue.The password hashing mechanism was updated in MySQL 4.1 to provide better security and to reduce the risk of passwords being intercepted. However, this new mechanism is understood only by the 4.1 server and 4.1 clients, which can result in some compatibility problems. A 4.1 client can connect to a pre-4.1 server, because the client understands both the old and new password hashing mechanisms. However, a pre-4.1 client that attempts to connect to a 4.1 server may run into difficulties. For example, a 4.0 mysql client that attempts to connect to a 4.1 server may fail with the following error message:
shell> mysql -h localhost -u root
Client does not support authentication protocol requested
by server; consider upgrading MySQL client
So, security of your database driven apps would benefit from an update to the database clients. This might be very important to some clients operating in production web server environments.
Keep up the good work RunRev,
