This is very interesting. My issue with mySQL is that I am running on a Windows 7 box, and there is no support for SSH in the Oracle version (or there wasn't last time I checked.) There *are* builds that do support it, but the weeds in that swamp are thick, and after several days of trying to get that working I gave up.
Bob S > On Mar 10, 2022, at 10:55 , matthias rebbe via use-livecode > <use-livecode@lists.runrev.com> wrote: > > You are right. > > You invoke the SSH in a terminal on that machine that shall communicate with > the MySQL database on a remote server. > LC then connects to itself (127.0.01) using the port you've used in the > command for ssh connection, in my example 6102. > That's it. > > As more and more servers do not allow remote MySQL access due to security > restrictions, SSH tunneling or a solution like the one Bob has created are > the only way. Whereby the SSH tunneling would allow a real direct > communication. Which one is better, i do not know. It depends on the needs of > the customer and also what software is available. > > > > >> Am 10.03.2022 um 19:11 schrieb Ben Rubinstein via use-livecode >> <use-livecode@lists.runrev.com>: >> >> Yes, my case is that the database is on a hosted platform which only >> supports access over SSH. >> >> My reading of your document, Matthias, is that we simply invoke SSH in a >> terminal, and then LiveCode/revOpenDatabase uses that tunnel automatically >> because the database host is at the same address. Can that be right? Or does >> this only work with LiveCode server? >> >> Ben >> >> On 10/03/2022 16:42, matthias rebbe via use-livecode wrote: >>> There is nothing wrong with your method. But there might be situations >>> where you need direct access to the MySQL database, e.g. you are using 3rd >>> party software (in my case SQLPro Studio) or libraries. I have a customer >>> who is using a special Delphi library that only supports direct connections. >>> Okay that is not the case when using Livecode. But there might be servers >>> that do not run Livecode Server. In this case you cannot use your solution. >>> In this case SSH tunneling would be a safe solution. >>>> Am 10.03.2022 um 17:14 schrieb Bob Sneidar via use-livecode >>>> <use-livecode@lists.runrev.com>: >>>> >>>> I am not sure what SSH tunneling is, but I did a proof of concept where I >>>> had an LC client app communicating with an LC server app that encrypted >>>> the data at the client end before sending it, and the server end decrypted >>>> it. I just used non-secured sockets. I used AES encryption with a key only >>>> I know, and a method for corrupting the data in a way only the server can >>>> "cleanse". >>>> >>>> I suppose some may advise me on what is wrong with this method, and I >>>> welcome the input, but it worked for me. No unencrypted data went "over >>>> the wire". >>>> >>>> The reason I developed this method is because I do not want to deal with >>>> expiring security certificates or secure websites to handle the data >>>> transfer. The method works out of the box. >>>> >>>> Bob S >>>> >>>> >>>>> On Mar 10, 2022, at 03:34 , Ben Rubinstein via use-livecode >>>>> <use-livecode@lists.runrev.com> wrote: >>>>> >>>>> >>>>> I need to access a (MySQL) database on a remote service - which has to be >>>>> done over an SSH tunnel. >>>>> >>>>> Has anyone done this in LiveCode? Is it trivial/possible/impossible? >>>>> >>>>> TIA, >>>>> >>>>> Ben >>>>> >>>>> _______________________________________________ >>>>> 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 > > > _______________________________________________ > 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
