This is definitely a bug and it still exists. Why was this closed without a fix?
Steps to Reproduce:
- Create an SSH2 key pair using the default settings with 'ssh-keygen' on OS X 10.8 - this results in a AES-128-CBC encrypted key.
- Add the public key to server's authorized keys and log in via SSH in Terminal to verify the new key pair is working.
- Attempt to use the same key to log in with (S)FTP or SshConsole plugins results in multiple (4-5) prompts for the key's password even if it is correctly entered
- jEdit appears to give up on public key authentication and falls back to keyboard interactive - resulting in an "Auth Fail".
Expected Result: Password prompt asks for correct password and logs in to the server when it's given
Log in to post a comment.