I had a private ssh key with and I’m trying to setup the SSH connection, but getting the error that it can’t connect because a passphrase is required. I have put the passphrase into the passphrase dialog on the “Create New SSH connection” dialog. Since that repeatedly did not work, I removed the passphrase from the private key – and it still complains that it can’t connect because a passphrase is required.
Since the private key does NOT currently require a key, I’m not sure what the UI is complaining about…
Most likely the passphrase did not get removed properly or the libssh2 library that VisualGDB is using fails to recognize it.
We recommend checking the “setup public key automatically” button to let VisualGDB generate a private key, store it in a Windows key container (automatically protected by your Windows account password) and use it automatically.
I’ve got a similar issue. When i use putty with my private key and a user i can properly login. The remote server ask me for the passphrase and after it works. With smartty it doesn’t works at all, weither i enter the passphrase into connection wizard or not.
We have investigated this further and it looks like one of the recent OpenSSL releases broke backward compatibility in the logic related to RSA keys. We have rebuilt the libssh2 library using an older OpenSSL and it should work normally.
Please try this build: VisualGDB-220.127.116.117.msi
Sorry, we only provide support to users of our commercial products like VisualGDB. We will eventually release an updated version of SmarTTY that will include the fix, but we cannot give any timelines on that, sorry.