There are also free MySQL Connectors/ODBC available for different operating systems. The current ones are for Server 8.0,5.7 and 5.6.
https://dev.mysql.com/downloads/connector/odbc/ They connectors can be downloaded without the need to be logged in. So no need for an account registration at dev.mysql.com Maybe this is an option instead of lowering the encryption level? Matthias - Matthias Rebbe Life Is Too Short For Boring Code > Am 26.08.2020 um 16:08 schrieb panagiotis merakos via use-livecode > <use-livecode@lists.runrev.com>: > > Hello all, > > This is because MySQL 8 supports a stronger authentication method based on > SHA256, and this method is used by default. > > LiveCode (as well as some other MySQL connectors/clients) do not support > this authentication method yet. In this case, you could configure your > MySQL installation to use the legacy authentication (password encryption) > method. > > See the suggested answers in this link: > https://stackoverflow.com/questions/50093144/mysql-8-0-client-does-not-support-authentication-protocol-requested-by-server/50961428 > > Hope this helps. > > Kind regards, > Panos > -- > > On Tue, 25 Aug 2020 at 18:41, Bob Sneidar via use-livecode < > use-livecode@lists.runrev.com> wrote: > >> mySQL for which platform? Last I checked, the build for Windows did NOT >> support encryption. There is a special branch that does, but I could never >> get it to work. >> >> What I came up with is an agent that resides on the SQL server, built in >> Livecode that listens for connections. It then handles the queries locally >> and returns the data. >> >> The client and Server encrypt the data before sending it using a method >> only I know, so it’s very secure. The communications are done but I haven’t >> done the actual query side yet. That will be a half day’s work at most. >> >> I think this client server approach is far better than native encryption, >> because I control the method and use a technique where even if someone >> tried brute force, or somehow discovered the key, they still could not >> decrypt the data, and wouldn’t know why. >> >> Bob S >> >> >> On Aug 24, 2020, at 3:25 PM, Heriberto Torrado via use-livecode < >> use-livecode@lists.runrev.com<mailto:use-livecode@lists.runrev.com>> >> wrote: >> >> Dear livecode programmers, >> >> For a few years we ran an internal app that accessed a MariaDB database >> (no PHP or LiveCode Server middleware, just a raw connection) using SSL. >> The server running the database is old, so we moved to a new one. >> >> The new one comes with a Mysql 8 Database instead of MariaDB and the SSL >> encryption suddenly stopped working. >> >> The new MYSQL database has a working SSL encryption cert (Let's encrypt). >> >> There are the tests: >> >> *From the server:* >> >> _______________________________________________ >> use-livecode mailing list >> use-livecode@lists.runrev.com >> Please visit this url to subscribe, unsubscribe and manage your >> subscription preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode >> > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
