MySQL Workbench 5.2 and SSH Mini-FAQ

MySQL Workbench provides secured access to MySQL Instances and Servers using SSH. The follow FAQ formated blog post shows a few details on what this is and how it works.

What is SSH?
A secure shell and communications tool

Secure Shell

• Replaces older insecure telnet, rsh, rlogin, rcp
• Provides the same functionality with added security.
• Avoids passing clear text user-ids & passwords
• Supports strong encryption for user authentication

Secure communications

• All TCP traffic sent through ssh can be strongly encrypted.
• Means that various TCP protocols can be given the same strong level of encryption as the ssh channel.

How is SSH used in Workbench?
Two ways

• As a secure communication tunnel for Direct MySQL connections
• As a method to remotely monitor and manage MySQL instance via SSH shell commands.

Where is SSH configured in Workbench?
Again 2 places

• Creating/Editing MySQL DB Connections

• Creating/Editing MySQL Server Instances (for remote Adminitration)

How does this work?
(click image to expand size)

When Workbench is setup with SSH

WB SQL Editor and Datamodel will use

1. Tunneled MySQL TCP Connections

MySQL Admin will use both

1. SSH Shell
   Runs MySQL related OS commands
2. Tunneled MySQL TCP Connections
   Connect and execute SQL-based  commands within MySQL Instance

What components are used in Workbench to provide its SSH support?

MySQL Workbench uses the the 100% Python-based Paramiko project to deliver its SSH capabilities.

To learn more about Paramiko >> http://www.lag.net/paramiko/

As always – hope this helps and look forward to any feedback or comments.