Re^2: Tunneling DBD::mysql connections over SSH without using external programs

[wwinfrey]

Right, I am very familiar with that technique. However, if you'll note from my post, my design goals dictate that I establish the tunneled connection without the use of exec() or open() calls to system binaries like the SSH client binary (/usr/bin/ssh) or socat.

I am not looking for how to do this from the shell; I am looking to do this completely from within the confines of my Perl application, mostly for portability issues, but also because this "application" I'm working on will be implemented as a custom module in an API I am designing.

Dependence on external programs in this situation seems sloppy and hard to maintain. I am looking for my fellow developers to simply "use" my module and not have to worry about installing anything else besides other Perl modules.

[salva]

Then, there is only a realistic way to do that: write your own ssh implementation using Net::SSH2 able to redirect connections on a TCP port to the remote MySQL port trough SSH.

Then in your module run this proxy in a new thread or process.

[wwinfrey]

I concur, Salva, that this is the approach I need to take. I'm more inclined to use Net::OpenSSH as it seems the most portable (and, as was pointed out by Krambambuli below, all the other modules are wrappers to one degree or another for external binaries). In my response below I distilled the issue down to "How do you make DBI connect with DBD::mysql over Net::OpenSSH tunnels ?" and I suppose that's the crux of the challenge.

[salva]

Net::OpenSSH does not work on Windows.

If you just want to run a tunnel, you could use the native ssh client from your OS on Unix and on Windows use PuTTY's plink which could be distributed with your module. IIRC, it doesn't have any dependency.