Re: Secure connection to SQL Server from Perl DBI

This sort of problem is often solved using an ssh tunnel. For example, instead of connecting to server:1234, you connect to localhost:1234 which was setup as a tunnel to server:1234. This solution involves running a bit of software on both the client (putty) and the server (???).

Comment on Re: Secure connection to SQL Server from Perl DBI Download Code

Replies are listed 'Best First'.
Re^2: Secure connection to SQL Server from Perl DBI by afoken (Chancellor) on May 30, 2009 at 23:00 UTC
the server (???) sshd from cygwin should to the trick, like one of the many other SSH server implementations for Win32. Sometimes, a friendly Linux or BSD machine near the server can also help, running the ssh server, tunnelling a port to the windows server. In PuTTY, specify windowsbox.remote.lan:1433 (not* localhost) as tunnel destination when connecting to linuxbox.remote.lan. It may look strange, but it works (unless linuxbox and windowsbox are separated from each other by a firewall). With the openssh command line client, it should look something like this: `ssh -L 1433:windowsbox.remote.lan:1433 joe@linuxbox.remote.lan` Connect to localhost:1433 and you should see the SQL server as long as the ssh connection is alive. The command line for PuTTYs plink utility should look nearly the same. Alexander -- Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)	[reply] [d/l]

Replies are listed 'Best First'.

Re^2: Secure connection to SQL Server from Perl DBI
by afoken (Chancellor) on May 30, 2009 at 23:00 UTC

the server (???)

sshd from cygwin should to the trick, like one of the many other SSH server implementations for Win32.

Sometimes, a friendly Linux or *BSD machine near the server can also help, running the ssh server, tunnelling a port to the windows server. In PuTTY, specify windowsbox.remote.lan:1433 (not localhost) as tunnel destination when connecting to linuxbox.remote.lan. It may look strange, but it works (unless linuxbox and windowsbox are separated from each other by a firewall). With the openssh command line client, it should look something like this:

ssh -L 1433:windowsbox.remote.lan:1433 joe@linuxbox.remote.lan

Connect to localhost:1433 and you should see the SQL server as long as the ssh connection is alive. The command line for PuTTYs plink utility should look nearly the same.

Alexander

--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)

[reply]
[d/l]