RE: Strange behavior between Mysql, MariaDB and SSL.

[Heriberto Torrado via use-livecode]

Thanks Mattias,

 

I appreciate your knowledge.

 

You are very useful and kind (as always).

 

Best,

Hery

 

From: matthias_livecode_150...@m-r-d.de  
Sent: Thursday, August 27, 2020 12:09 PM
To: How to use LiveCode 
Cc: htorr...@networkdreams.net
Subject: Re: Strange behavior between Mysql, MariaDB and SSL.

 

Heriberto,

 

i just tried the ODBC drivers from Oracle here with MacOS X and MariaDB.

 

If you would like i can list the needed steps:

 

1. download and install the drivers for your operating system

 

2. Open ODBC Manager on Mac, i am not sure how this is called in English for 
the Windows app, but if you search for ODBC in the search field of Windows 
you'll get the configuration tool listed.

 

3. Add a new User or System DSN. You can select between Ansi and Unicode driver

 

4.1 In the following configuration dialog enter a name for the DNS, e.g. 
HeribertoDSN

4.2 Add the Keyword 'SERVER' and add the name or the ip address of the DB 
Server as value, e.g. HeribertoDB

If the DB is not using the standard port, then please add the port also. e.g. 
192.168.1.1:3308

4.3 Add the Keyword DATABASE and enter the name of the DB as value

There are several other keywords you can use. But the above are the basic ones 
you need.

 

now use 

revOpenDatabase("odbc", "HeribertoDSN","HeribertoDB",dbUsername,dbPassword,)

 

replace dbUsername and dbPassword with the user credentials for the DB.

 

You could also add the keywords USERNAME and PASSWORD in the DSN configuration 
from step 4, but i would do that only for testing.

 

Btw. the documentation for the ODBC driver can be found here.

 

Regards,

 

Matthias Rebbe
Life Is Too Short For Boring Code





Am 27.08.2020 um 01:03 schrieb Heriberto Torrado mailto:htorr...@networkdreams.net> >:

 

Hi Matthias,

Do you mean connecting to MySQL using ODBC instead of the built-in LiveCode 
MySQL client?

Best,
Hery

-Original Message-
From: use-livecode mailto:use-livecode-boun...@lists.runrev.com> > On Behalf Of matthias rebbe 
via use-livecode
Sent: Wednesday, August 26, 2020 10:42 AM
To: How to use LiveCode mailto:use-livecode@lists.runrev.com> >
Cc: matthias_livecode_150...@m-r-d.de 
<mailto:matthias_livecode_150...@m-r-d.de> 
Subject: Re: Strange behavior between Mysql, MariaDB and SSL.

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 
mailto: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 <mailto: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%3cmailto: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 w

RE: Strange behavior between Mysql, MariaDB and SSL.

[Heriberto Torrado via use-livecode]

Thanks Mattias,

Yes, it is an internal app, but I have a few users using Android.

Best,
Hery

-Original Message-
From: use-livecode  On Behalf Of
matthias rebbe via use-livecode
Sent: Thursday, August 27, 2020 11:55 AM
To: How to use LiveCode 
Cc: matthias_livecode_150...@m-r-d.de
Subject: Re: Strange behavior between Mysql, MariaDB and SSL.

You are correct.
But as Heriberto wort, it is an inhouse app, i thought using ODBC connector
from Oracle might be better than lowering the security level of the
database.



-
Matthias Rebbe
Life Is Too Short For Boring Code

> Am 27.08.2020 um 17:40 schrieb Bob Sneidar via use-livecode
:
> 
> Just a heads up, ODBC is a local service, not a network protocol. You have
to create a DSN on the client OS which handles the network communications
for you. So every client that connects will need to have this DSN set up
first. For the experienced, this is no big deal, but for the first time
initiate it can be confusing.
> 
> Bob S
> 
> 
> On Aug 26, 2020, at 4:03 PM, Heriberto Torrado via use-livecode
mailto:use-livecode@lists.runrev.com>> wrote:
> 
> Hi Matthias,
> 
> Do you mean connecting to MySQL using ODBC instead of the built-in
LiveCode MySQL client?
> 
> Best,
> Hery
> 
> ___
> 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

RE: Strange behavior between Mysql, MariaDB and SSL.

[Heriberto Torrado via use-livecode]

Got it, but it could be a problem for mobile users.

I know how to create a ODBC connection on Windows/Linux/Mac, but doing it on
Android it's out of my reach.

Best,
Hery

-Original Message-
From: use-livecode  On Behalf Of Bob
Sneidar via use-livecode
Sent: Thursday, August 27, 2020 11:41 AM
To: How to use LiveCode 
Cc: Bob Sneidar 
Subject: Re: Strange behavior between Mysql, MariaDB and SSL.

Just a heads up, ODBC is a local service, not a network protocol. You have
to create a DSN on the client OS which handles the network communications
for you. So every client that connects will need to have this DSN set up
first. For the experienced, this is no big deal, but for the first time
initiate it can be confusing.

Bob S


On Aug 26, 2020, at 4:03 PM, Heriberto Torrado via use-livecode
mailto:use-livecode@lists.runrev.com>> wrote:

Hi Matthias,

Do you mean connecting to MySQL using ODBC instead of the built-in LiveCode
MySQL client?

Best,
Hery

___
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

Re: Strange behavior between Mysql, MariaDB and SSL.

[matthias rebbe via use-livecode]

Heriberto,

i just tried the ODBC drivers from Oracle here with MacOS X and MariaDB.

If you would like i can list the needed steps:

1. download and install the drivers for your operating system

2. Open ODBC Manager on Mac, i am not sure how this is called in English for 
the Windows app, but if you search for ODBC in the search field of Windows 
you'll get the configuration tool listed.

3. Add a new User or System DSN. You can select between Ansi and Unicode driver

4.1 In the following configuration dialog enter a name for the DNS, e.g. 
HeribertoDSN
4.2 Add the Keyword 'SERVER' and add the name or the ip address of the DB 
Server as value, e.g. HeribertoDB
If the DB is not using the standard port, then please add the port also. e.g. 
192.168.1.1:3308
4.3 Add the Keyword DATABASE and enter the name of the DB as value
There are several other keywords you can use. But the above are the basic ones 
you need.

now use 
revOpenDatabase("odbc", "HeribertoDSN","HeribertoDB",dbUsername,dbPassword,)

replace dbUsername and dbPassword with the user credentials for the DB.

You could also add the keywords USERNAME and PASSWORD in the DSN configuration 
from step 4, but i would do that only for testing.

Btw. the documentation for the ODBC driver can be found here.

Regards,

Matthias Rebbe
Life Is Too Short For Boring Code

> Am 27.08.2020 um 01:03 schrieb Heriberto Torrado :
> 
> Hi Matthias,
> 
> Do you mean connecting to MySQL using ODBC instead of the built-in LiveCode 
> MySQL client?
> 
> Best,
> Hery
> 
> -Original Message-
> From: use-livecode  On Behalf Of 
> matthias rebbe via use-livecode
> Sent: Wednesday, August 26, 2020 10:42 AM
> To: How to use LiveCode 
> Cc: matthias_livecode_150...@m-r-d.de
> Subject: Re: Strange behavior between Mysql, MariaDB and SSL.
> 
> 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 
>> :
>> 
>> 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 dat

Re: Strange behavior between Mysql, MariaDB and SSL.

[matthias rebbe via use-livecode]

Of course it was meant to be

"But as Heriberto wrote,.."

-
Matthias Rebbe
Life Is Too Short For Boring Code

> Am 27.08.2020 um 17:55 schrieb matthias_livecode_150...@m-r-d.de:
> 
> You are correct.
> But as Heriberto wort, it is an inhouse app, i thought using ODBC connector 
> from Oracle might be better than lowering the security level of the database.
> 
> 
> 
> -
> Matthias Rebbe
> Life Is Too Short For Boring Code
> 
>> Am 27.08.2020 um 17:40 schrieb Bob Sneidar via use-livecode 
>> :
>> 
>> Just a heads up, ODBC is a local service, not a network protocol. You have 
>> to create a DSN on the client OS which handles the network communications 
>> for you. So every client that connects will need to have this DSN set up 
>> first. For the experienced, this is no big deal, but for the first time 
>> initiate it can be confusing.
>> 
>> Bob S
>> 
>> 
>> On Aug 26, 2020, at 4:03 PM, Heriberto Torrado via use-livecode 
>> mailto:use-livecode@lists.runrev.com>> wrote:
>> 
>> Hi Matthias,
>> 
>> Do you mean connecting to MySQL using ODBC instead of the built-in LiveCode 
>> MySQL client?
>> 
>> Best,
>> Hery
>> 
>> ___
>> 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

Re: Strange behavior between Mysql, MariaDB and SSL.

[matthias rebbe via use-livecode]

You are correct.
But as Heriberto wort, it is an inhouse app, i thought using ODBC connector 
from Oracle might be better than lowering the security level of the database.



-
Matthias Rebbe
Life Is Too Short For Boring Code

> Am 27.08.2020 um 17:40 schrieb Bob Sneidar via use-livecode 
> :
> 
> Just a heads up, ODBC is a local service, not a network protocol. You have to 
> create a DSN on the client OS which handles the network communications for 
> you. So every client that connects will need to have this DSN set up first. 
> For the experienced, this is no big deal, but for the first time initiate it 
> can be confusing.
> 
> Bob S
> 
> 
> On Aug 26, 2020, at 4:03 PM, Heriberto Torrado via use-livecode 
> mailto:use-livecode@lists.runrev.com>> wrote:
> 
> Hi Matthias,
> 
> Do you mean connecting to MySQL using ODBC instead of the built-in LiveCode 
> MySQL client?
> 
> Best,
> Hery
> 
> ___
> 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

Re: Strange behavior between Mysql, MariaDB and SSL.

[Bob Sneidar via use-livecode]

Just a heads up, ODBC is a local service, not a network protocol. You have to 
create a DSN on the client OS which handles the network communications for you. 
So every client that connects will need to have this DSN set up first. For the 
experienced, this is no big deal, but for the first time initiate it can be 
confusing.

Bob S


On Aug 26, 2020, at 4:03 PM, Heriberto Torrado via use-livecode 
mailto:use-livecode@lists.runrev.com>> wrote:

Hi Matthias,

Do you mean connecting to MySQL using ODBC instead of the built-in LiveCode 
MySQL client?

Best,
Hery

___
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

RE: Strange behavior between Mysql, MariaDB and SSL.

[Heriberto Torrado via use-livecode]

Hi Matthias,

Do you mean connecting to MySQL using ODBC instead of the built-in LiveCode 
MySQL client?

Best,
Hery

-Original Message-
From: use-livecode  On Behalf Of 
matthias rebbe via use-livecode
Sent: Wednesday, August 26, 2020 10:42 AM
To: How to use LiveCode 
Cc: matthias_livecode_150...@m-r-d.de
Subject: Re: Strange behavior between Mysql, MariaDB and SSL.

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 
> :
> 
> 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


___
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

RE: Strange behavior between Mysql, MariaDB and SSL.

[Heriberto Torrado via use-livecode]

Hi Panagiotis,

It makes sense, I'm going to try it.

Thank you very much for your recommendations.
I would like to say that this list is great.

Best,
Hery


-Original Message-
From: use-livecode  On Behalf Of 
panagiotis merakos via use-livecode
Sent: Wednesday, August 26, 2020 10:09 AM
To: How to use LiveCode 
Cc: panagiotis merakos 
Subject: Re: Strange behavior between Mysql, MariaDB and SSL.

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

RE: Strange behavior between Mysql, MariaDB and SSL.

[Heriberto Torrado via use-livecode]

Hi Bob,

It worked from Linux, Mac, and Windows.

Your idea sounds really good, but to be honest, I'm pretty busy these days and 
I wouldn't like  to deal with making middleware.
I just looking for a quick fix.

Maybe in the future, I’ll have to do it.


Best,
Hery

-Original Message-
From: use-livecode  On Behalf Of Bob 
Sneidar via use-livecode
Sent: Tuesday, August 25, 2020 11:40 AM
To: How to use LiveCode 
Cc: Bob Sneidar 
Subject: Re: Strange behavior between Mysql, MariaDB and SSL.

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 
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

Re: Strange behavior between Mysql, MariaDB and SSL.

[matthias rebbe via use-livecode]

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 
> :
> 
> 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>
>> 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

Re: Strange behavior between Mysql, MariaDB and SSL.

[panagiotis merakos via use-livecode]

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>
> 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

Re: Strange behavior between Mysql, MariaDB and SSL.

[Bob Sneidar via use-livecode]

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 
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