Comments on: Protecting MySQL Sessions With SSH Port Forwarding (Part 1)

By: Yung Moel

Yung Moel — Tue, 04 Jan 2011 00:03:42 +0000

Couldn’t agree much more with that, really interesting content. Thank You.

By: Johnson Seitzinger

Johnson Seitzinger — Thu, 04 Mar 2010 17:15:27 +0000

If you want to take what other cannot offer than right choise is to go to linuxhostinghub.com and see what are your options.

By: Tree of Life

Tree of Life — Thu, 24 Sep 2009 14:25:26 +0000

I have to say, SSH was the best thing they ever came out with. You can’t beat its security nor its reliabilty.

By: Patrick

Patrick — Wed, 21 Jan 2009 09:34:54 +0000

Nice article.

Here is a complimentary article that explains how to incorporate SSH into your application using a library rather than via the command line:

http://georgelantz.com/2007/09/10/access-mysql-through-ssh-tunnel-in-a-windows-net-application/

Here is a .NET SSH library that can do tunneling:

http://www.tamirgal.com/home/dev.aspx?Item=SharpSsh

By: WaQas

WaQas — Thu, 06 Nov 2008 11:11:25 +0000

if we use plink.exe with command line .. so i want to know that is our SSH password will safe when we publish our software to general public????

please try to reply me as soon as possible..

By: Kintat

Kintat — Wed, 27 Feb 2008 03:41:04 +0000

I found it conceptually difficult to grasp the settings of the SSH-tunnel setting in the PuTTY screenshot, particularly the value for the box “Destination” (within “Port forwarding” area). This was so until I realise its exact meaning:

“Destination” means “destination as seen from the eye of the server hosting your ssh server, once your SSH connection to it is established.”

Thus, if your ssh server listening at port 22 is hosted in http://www.yoursshsvr.org, and *IF* your intended destination socket of your forwarded TCP connection is (www.yoursshsvr.org:3306), then the followings should be somewhat(?) equivalent:

1) Destination box set to “www.yoursshsvr.org:3306″

2) Destination box set to “127.0.0.1:3306″ (’127.0.0.1′ doesn’t mean your client machine running PuTTY; here it means http://www.yoursshsvr.org)

But I did experience a big difference myself between 1) & 2), with my PuTTY/mySQL Administrator run from Win2K3:
– when using 1) I always failed and got an 2013 error;
– when using 2) I succeeded in my connecting to http://www.yoursshsvr.org‘s mysql server at its 3306 port.

(to avoid confusing with any side issues I had removed all iptables rules from http://www.yoursshsvr.org before the attempted connections, and my mySQL user is with the ‘%’ in its host field in table ‘user’)

Hope this helps, and please correct me if it still lacks precision.

By: Chris

Chris — Sun, 13 Jan 2008 22:52:55 +0000

Thanks for this posting, it will be helpful to me to get Crystal Reports running on a hosted MySQL database.

That said, can the author of this article provide more detail around how to setup the ODBC on a local Windows machine to work with the SSH connection? I set up my SSH connection as explained above, but I am not sure what to do with the desktop ODBC. I downloaded and installed the MySQL 3.51 ODBC driver, then went to the ODBC and tried to set up a connection and it complained.

Any help or direction to help on this matter would be greatly appreciated.

Thanks,
Chris