SSH Authentication Changes in Transmit 5.6.4
At Panic we are always balancing security, ease of use and of course fixing bugs. In Transmit 5.6.4 and later we’ve made some changes to improve security while fixing some bugs in Transmit when connecting to an SFTP server. As a result, Transmit will now use key files assocated with a server before passwords saved in Transmit favorites.
What is a key, you ask? It’s a file you can think of as a “super password” that is unique to your computer and the server. Odds are, you set this up on your computer and have completely forgotten about it, that’s why you’re reading this article. Since keys are more secure than passwords, Transmit now favors using them when logging in to your servers.
Due to these changes, it’s possible you may find yourself in a situation where you are prompted for an SSH key passphrase upon connecting to any SFTP server, like so:
Another possibility is that you may get an
Authentication Failed error with a miscellaneous error code showing up in the Transcript log.
If you find yourself in this situation, it is likely that you have a key defined for this connection in your SSH config file, whether you meant to or not.
Check Your SSH Config File For Accuracy
First, open your config file in a text editor of your choosing. Here’s how:
- In Finder’s menubar, select
Go to folderfrom the
- In the box that appears, enter the following and click Go:
- Right click
configand open it in a text editor.
*) configurations in your SSH config are often not ideal and will cause Transmit to prompt you for a passphrase should you have an encrypted key configured here with a wildcard address. One common situation would be for Github, as their documentation currently instructs you to configure things this way. Here’s an example of what this would look like in your config file:
Host * AddKeysToAgent yes UseKeychain yes IdentityFile ~/.ssh/id_rsa
The entry above will cause Transmit to prompt you for your SSH Key passphrase with every SFTP connection, as this key is explicitly defined for all addresses due to the wildcard.
Since the config file is used by many different apps (Transmit, Terminal, Coda, Git clients, etc.), this is not an optimal way to define the key in your config file. For the most part, Transmit attempts to match the behavior of SSH on the command line. If you attempt to SSH into the same server on the command line (with a wildcard address in your config file like the example above), you’ll be prompted for the passphrase the same as you would in Transmit.
In an ideal scenario, rather than using a wildcard for the host entry, you would use only the address to which the key actually applies. Using the Github example above as the server in question, that entry in your config file would look like this:
Host github.com AddKeysToAgent yes UseKeychain yes IdentityFile ~/.ssh/id_rsa
In this case, Transmit would only prompt you for your SSH key passphrase when connecting to
If you were previously using a wildcard entry deliberately to use your key for multiple addresses, you can add those all to the host entry separated by spaces, avoiding the wildcard scenario and still allowing multiple hosts for a single key entry. Here’s one possible example:
Host github.com mysite.com myserver.com AddKeysToAgent yes UseKeychain yes IdentityFile ~/.ssh/id_rsa
TL;DR: Now that Transmit 5.6.4 uses explicitly-defined keys in your config file (just like SSH on the command line) make sure that the
Host entry for keys defined in your config file are only for the necessary addresses, not a wildcard.
For more information about how SSH keys work in Transmit or any other Panic app, please see our SSH key documentation.