many colleagues asked me, if it’s possible to use an ssh-agent for secure-gateway authentification (e.g. Pageant). Now it look’s like that didn’t work..
Is it planned to implement a feature like this in further versions?
there are no plans right now to include an ssh agent. Most of our users are storing the credentials in Royal TS documents. Can you provide some details why this is not an option for you or what the exact use case is?
Having the same issue here. I had high hopes for the Secure Gateway feature! Alas, it’s of no use for me as the private key needed for jump host authentication resides on a smartcard that is only usable via pageant.
Rebex, who is providing the components for terminal (SSH) and file transfer, is currently working on Pageant support. I’m not sure what exactly is covered and how it is working but as soon as they have something, we will see if and how we can integrate this into our product. Stay tuned.
I recently decided to try out ssh-agent forwarding and I’m surprised that I have to run a third party ssh agent outside of Royal TS, and also switch from Rebex terminal to PuTTY as Rebex doesn’t support ssh-key agent forwarding.
Royal TS takes on control of my SSH keys as credential objects but does not allow a ssh connect to do agent forwarding with those same credentials.
I’d really like to see:
Royal TS become an ssh-agent for credentials defined for a connection
Rebex support ssh-agent forwarding
This will allow me to ssh into my jump host, and then ssh from there to my other servers without having to control and distribute my ssh-keys all over the place. I don’t actually mine running a third-party ssh-agent (I use Simon Tatham’s Pagent) if the Royal TS default Terminal plug-in supported forwarding.
ssh-connections can use Pageant by enabling it in “Terminal application settings > Advanced > SSH Settings > Auth : Attempt Authentication using Pageant” using PuTTY plugin.
Secure Gateway entries still can’t use a ssh-agent like Pageant.
I think you should be able to prevent this dialog by putting storing Fingerprint and enable the Use Hostkey option in the PuTTY connection configuration: