SSH key agent doesn't work in OpenSSH mode

Hello,

Did you try pressing "start agent" with the OpenSSH mode? It should work for you. The warning icon is just to be informative, as we had users trying to use this mode without having OpenSSH installed on their machine.

As for running both agents at once, it should technically be possible but there are a few technicals aspects we would need to figure out, it's not as simple as just starting both at once. I will open a ticket for this.

Regards,

Thanks, yes I tried starting the agent, forgot to paste the screenshot with it. Clicking on "Start Agent" results in the following error:

Hey,
you can verify whether the agent is installed and running on Windows by opening PowerShell and running:

Get-Service ssh-agent | Format-List Name,Status,StartType

Ideally, the output should look like this:

Name : ssh-agent
Status : Running

If the service is installed but not running, you can start it using :

Start-Service ssh-agent

Best regards,
Stephan

In addition to what my colleague Stephan asked, you could also open the performance profiler in the debug tab at level 1, and press "start agent". I'd like to see what error shows up in the profiler. Here is an example in my environment, where I don't have OpenSSH installed:

Regards,

Thank you, I did it and got the same result. I think this message is red herring. In my case the issue was that the Windows service "ssh-agent" was not running and I think RDM was unable to start it, because it would require administrator permissions (elevation) and I'm running RDM without elevation. I changed the service to "Automatic (delayed start)" and started it and then I was able to click "Start Agent" in RDM/SSH key agent and it loaded a key.

You may want to handle this scenario properly in RDM (i.e. start the service using elevation if necessary, and then automatically refresh the keys grid).

Thank you!

Thank you, that's good information. I will open a separate ticket for this and we will see what we can do. As far as I'm aware it's not possible to start a service that requires elevated privileges from a non-elevated application, which would mean RDM would need to start a separate process to do this.
In the short term, I will see if it's at least possible to mention in the error message to verify if the OpenSSH service is running, as that may at least lead the user toward a possible solution.

Regards,