You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on some tests, I find that termscp is unable to handle encrypted ssh keys. Functionality added as a result of #123 and #126 fails when ssh key, e.g. ~/.ssh/id_ed25519, requires a passphrase.
Usually you would decrypt the key once and make it available to applications via ssh-agent.
If you try to use an encrypted ssh key, you will get this error: authentication failed (could not find any suitable RSA key to authenticate with). Also, in the message, an ssh key need not be an RSA key.
The text was updated successfully, but these errors were encountered:
Description
Based on some tests, I find that
termscp
is unable to handle encrypted ssh keys. Functionality added as a result of #123 and #126 fails when ssh key, e.g.~/.ssh/id_ed25519
, requires a passphrase.Usually you would decrypt the key once and make it available to applications via ssh-agent.
If you try to use an encrypted ssh key, you will get this error:
authentication failed (could not find any suitable RSA key to authenticate with)
. Also, in the message, an ssh key need not be an RSA key.The text was updated successfully, but these errors were encountered: