This is possible already although it's not as elegant as it could be.
Use Pageant, which is part of the free PuTTY software, to load the key file into memory, then connect to the SFTP or SCP site using Opus. You'll still be prompted for a password (this is the inelegant part) but if you leave the field blank and just hit return you'll connect and authenticate using the private SSH key that's in memory.
Update: If you save the site entry in Opus with any non-empty password (e.g. just a space or some other character), then you can avoid being prompted for the password.
ok, this is a possibility. But - I'm really sorry - I have a few servers, that behave that way. And loading the key into memory manually... won't this bring problems if I try to connect to two of such servers simultaniously?
You can load as many keys into memory as you need so that shouldn't be a problem.
Having to load them in advance via a separate program, rather than on-demand within Opus, isn't ideal though. If you send GPSoft a feature request I'll back up the report and, if needed, help get them a test site and key so they have something to work with.
(Coincidentally, I just had to look at this stuff for my work and have become somewhat familiar with it (enough to get my files copied from A to B). I was going to file a similar request eventually but haven't had time to write it up yet.)
A blast from the past, but did either of you submit a feature request in the end for assigning an SSH key file-path to an FTP site in the FTP address book ?
We have currently the problem that our access in our bank company changes and we have to connect to ONE server (access gateway) to get access to other servers.
For this access we need the openSSH.pub format, DSA (ssh2), Key length 1024 + passphrase. No other way.
I've just tried pageant to select the private key file (openSSH format) but it as not possible to read it.
It would be also great to support a save+remember of the passphrase to click on connect without getting a prompt for the passphrase which results in opening another file to get it because it is a string with 30 characters ...
I hope this will be implemented into one of the next release because I don't know how long the current situation (SFTP with password) will work - and I don't want miss DO !
Since our SFTP code is based on PuTTY it's unlikely anything that doesn't work in PuTTY will work in Opus. I seem to remember there being ways to convert private keys between the different formats, but it's a while since I personally set one up so I may be thinking of something unrelated.
I've tried puttygen.exe and was able to load an existing private key file. I got the message "Succesfully imported key (OpenSSH SSH-2 private key) To use this key with Putty, you need to use the "Save private key" command to save it in Putty's own format".
But when I look into the *.ppk file the original private key file is not saved in this file (but includes the public key).
Ok, I have a solution now, but it is not really nice.
At first - we have a lot of SSH public/private key pairs with passphrase - which has 30 positions (digits + letters created by random!).
With e.g. MindTerm (SSH client like Putty) I can save the passphrase of the private key file in a config file. Nice to have this option! A double click on the icon to start MindTerm by using the config file as parameter and the SSH starts (public-key incl. passphrase).
I can prepare Pageant to start with multiple SSH keyfiles (as I've just read at the.earth.li/~sgtatham/putty/0.6 ... ml#pageant - chapter 9.3.1) but I have to copy + paste or manually type the random generated passphrases. - which is nothing for a daily work for a developer which wants to connect to the development servers.
Also for at home to connect to my private server I would not like this - but I want to use the long random string as passphrase of course.
Maybe we will see a better solution in DO 12?
=> Selectable private key files of all possible formats floating around and storing the passphrase.
I didn't know but back in the days they told us how to do.
In the meantime I've asked the admins and it is not required. I was able to convert the encrypted private key files with puttygen / MindTerm and stored them without passphrase - and all works.
Apologies for the resurrection, but we just switched configs on our server and I finally need to use ssh keys. Am I correct to assume that DO still doesn't support ssh keys by itself and I must use Pageant?
We may add support for ssh keys without having to use Pageant in the future (but can't promise it at this stage). If we do, it'll be an option in the FTP Address Book for SSH sites, so should be easy to find.