-
-
Notifications
You must be signed in to change notification settings - Fork 71
Closed
Labels
backlogImplementation/fix not planned yetImplementation/fix not planned yetnew featureNew feature or requestNew feature or request
Milestone
Description
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.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
backlogImplementation/fix not planned yetImplementation/fix not planned yetnew featureNew feature or requestNew feature or request