LiveCode Forums.

As I understand it, RunRev uses a MySQL 4.0 version client to perform MySQL database operations (certainly under Linux anyway).

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.

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

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.

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,

Hi Rishi,

The Revolution crew addressed this in the latest version 2.7.2 - from the "What's New" file:

The MySQL driver is now linked against the latest version of the MySQL
client library (5.0.23).
The PostgreSQL driver is now linked against the latest version of the
PostgreSQL client library (8.1.3).
The ODBC driver is now linked against the latest version of iODBC (3.52.4)
on non-Windows platforms.
The Oracle driver remains unchanged, pending the release on a universal
binary version of the Oracle Instant Client SDK software.

In these cases, the database driver is statically linked with the client
libraries meaning there are no external dependencies on other libraries or
files. (In the case of ODBC, it still necessary to have the required ODBC
back-end drivers installed and data sources configured).

Hope this clarified the situation,

Jan Schenkel.

Thanks Jan,

The Revolution crew addressed this in the latest version 2.7.2

Oops, I am still using 2.5.1, but didn't notice this in the what's new...

The Linux version is still at 2.6.2 is it not? Are the database client libraries updated in 2.6.2 as well or is this update only in 2.7.2?

Still searching the Rev site for confirmation...

Hi Rishi,

The Linux version is still at 2.6.1, and won't be updated separately.
I'm sure you're not the only one hoping that the next revision of Rev (2.7.3) will herald the return of Linux and MacOS Classic, any day now...

Jan Schenkel.

Hello,

Same problem with Livecode 9.6.
Any workaround ? (I cannot change settings on the mysql server side).

Thanks

This thread was resurrected from 14 years ago. Can you describe what you're experiencing with LiveCode 9.6?

I am getting the same error.

Unable to connect to the database.
Client does not support authentication protocol requested by server; consider upgrading MySQL client.

I am using Livecode v. 9.5.1 and MySQL Community Server v. 8.0.19.