by pjkerpan » Sun Apr 15, 2012 11:50 am
Thanks for the attempts at helping.
The SSH manager creates keys, I don't want it to create keys.
When I use a Terminal to make an SSH tunnel I say:
sss -i <path to whatever private key I want> foouser@ip_address
I would like the same capability out of remoter - when I set up a connection I have to specify the attributes of the connection. It requires the host address, ssh username, ssh password, vnc password. I would like the option to provide a path for ssh key instead of ssh password right there.
Cloud computing has inverted the public/private key "workflow". People who control/own servers are not going to put your public keys in their server. As a result they make a key pair for you that they "control" (nominally), they put the public key in the server and they provide you with your "private" key.
I can make SSH tunnels and do port forwarding quite easily for VNC. I am looking for a solution for partners, customers who find that more challenging.