Home arrow MySQL arrow Page 2 - Using SSH in HeidiSQL and MySQL Query Browser: Encrypting Sessions

SSH Port Forwarding: The Solution - MySQL

Using a MySQL GUI (Graphical User Interface) makes it easier, more efficient and user-friendly to work with a MySQL database. The two most popular MySQL GUIs, HeidiSQL and MySQL Query Browser, have their default connections to any MySQL server “unencrypted.” This is a problem, but we're going to fix it; just keep reading.

  1. Using SSH in HeidiSQL and MySQL Query Browser: Encrypting Sessions
  2. SSH Port Forwarding: The Solution
  3. Step 1: Enable Port Forwarding in Putty for MySQL SSH Application
  4. Step 2: Configure your MySQL Graphical User Interface (GUI)
By: Codex-M
Rating: starstarstarstarstar / 2
May 04, 2010

print this article



Without encryption, it is said that your data (including your MySQL log-in information) will travel as packets on the Internet in "clear text format." If a hacker (or anyone) sniffs that data using a third-party application, he or she will immediately see and understand the information. If the sniffed data is your MySQL log-in, it can be compromised.

The solution is to encrypt packets using SSH is to employ "Port forwarding" techniques. It is illustrated in the screen shot below:

If a MySQL GUI (HeidiSQL or MySQL query browser) connects to your MySQL server "securely," the first thing that will happen is that it will use a local host port other than the one that your local MySQL server is using. MySQL commonly uses Port 3306 for its communications. If you are developer, chances are you have MySQL installed locally, which also uses Port 3306.

To prevent any possibility of conflict, it will use Port 3307 locally, which is then detected by an SSH Client (Putty) and "port forward" to Port 3306 in your remote MySQL server. Of course, before your SSH client can accomplish this task, it must first be connected to your remote SSH server, which is your web host.

To enable port forwarding, you need to configure Putty to accomplish that job. The result is that the SSH client will sit "in between" your MySQL GUI and your hosting MySQL server. All traffic traveling from your SSH client (in your local computer) to your remote MySQL server Port 3306 has been encrypted using SSH.

To summarize, your MySQL GUI uses local port 3307, which is "port forwarded" by the Putty SSH Client to your remote MySQL server using standard MySQL port 3306. This is how the encryption of MySQL data has been accomplished.

>>> More MySQL Articles          >>> More By Codex-M

blog comments powered by Disqus
escort Bursa Bursa escort Antalya eskort


- Oracle Unveils MySQL 5.6
- MySQL Vulnerabilities Threaten Databases
- MySQL Cloud Options Expand with Google Cloud...
- MySQL 5.6 Prepped to Handle Demanding Web Use
- ScaleBase Service Virtualizes MySQL Databases
- Oracle Unveils MySQL Conversion Tools
- Akiban Opens Database Software for MySQL Use...
- Oracle Fixes MySQL Bug
- MySQL Databases Vulnerable to Password Hack
- MySQL: Overview of the ALTER TABLE Statement
- MySQL: How to Use the GRANT Statement
- MySQL: Creating, Listing, and Removing Datab...
- MySQL: Create, Show, and Describe Database T...
- MySQL Data and Table Types
- McAfee Releases Audit Plugin for MySQL Users

Developer Shed Affiliates


Dev Shed Tutorial Topics: