New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lookup of password for private key fails in Keychain #5148
Comments
I can also confirm this issue, with same diagnosis after upgrade to 3.6.1 from 3.5.1. Mac OS X 10.6.4. Command line SFTP to the same servers still remains functional. Please advise if additional information required; I'll be reverting to 3.5.1 in interim. |
Replying to [comment:5 dkocher]:
"Username set in the bookmark?" Absolutely - otherwise it'd be difficult for the remote machine to know where to look for the public key [generally in ~username/.ssh/authorized_keys]. I'm gonna be occupied for the next few hours, but I'll endeavour to pull down the trunk and build it to see if 9bbc7bd behaves correctly. |
I can confirm this issue. Just updated and can't login to my servers anymore. |
I can tell you that I feel the bug when connecting to a Mac OS X Server box, a Debian Linux and a CentOS, so it does not seem to depend on the serverside OS. |
I don't know if this helps, probably not, but this is what ends up in my Console
|
I have downgraded to 3.5.1 now which you can find on Apples software page http://apple.com/downloads/macosx/internet_utilities/cyberduck.html |
Replying to [comment:10 https://www.google.com/accounts/o8/id?id=aitoawmq5en6knjocnovu6ny_jf5ezv90ugs26w]:
Previous releases are always available at http://cyberduck.ch/changelog/ |
Can you confirm that in your private key at the beginning there is no such thing as |
There is:
|
Replying to [comment:13 https://www.google.com/accounts/o8/id?id=aitoawmq5en6knjocnovu6ny_jf5ezv90ugs26w]:
From what I know this means your private key is password protected. |
The issue is that our lookup for the password of the private key in the keychain fails. (We previously looke for the password in the keychain with the abreviated filename of the private key (such as |
There appears to be a regression in build 7035 that leads to this bug once again rearing its unfortunate head. Have reverted back to build 7015, as the problem doesn't exist in that nightly build. |
Replying to [comment:18 http://theonlycueball.myopenid.com/]:
Decided to break backward compatibility with SSHKeychain in 570c9c0. You have to reenter the SSH private key password. |
After I encountered this bug again some time ago, I stopped updating nightly builds again and stuck with build 8001 [which works for me.] Since it was deemed "fixed", I really wasn't about the belabour the point again in case there was just something hinky with my config. Apparently I'm not the only one seeing this problem still... Perhaps a unit test for this case to avoid the issue in future? :-) |
Cyberduck (tried 4.1 (8911)) should still IMHO be finding the password for my private key in Keychain. In OS X 10.6 Snow Leopard at least, when you open an SSH connection through the Terminal with the In other words, OS X does have a method for storing and reading the password for private keys in the Keychain without any need of third party software such as SSHKeychain. It would be nice if Cyberduck detected OS X-saved password to my private key in the Keychain, and asked me for access to it, instead of asking the password to my private key (just as a note, Transmit 4 does). |
Replying to [comment:24 elmimmo]:
Great suggestion. We should try to be interoperable with Terminal.app here. |
Replying to [comment:25 dkocher]:
OpenSSH interoperability in 51d514d. |
How does 51d514d work? I downloaded the nightly Cyberduck-9393 but I am still asked to specify a private key file, and even if manually specified, Keychain access never asks me to unlock the keychain where the password to my private key resides. |
I just updated from 3.5.1 to 3.6.1
I connect to all of my servers via SFTP and key authentication (passwords are disabled on the server). My private key has no password, and never did.
As soon as I updated to 3.6.1, Cyberduck started to ask me for my private key password. Clicking the default button leaving the password empty does not solve the issue. I rechecked in Terminal and my key is still unprotected by passwords, and I can log into my servers via ssh.
Attachments
jan_dialog.png
(43.4 KiB)jan_settings.png
(54.9 KiB)The text was updated successfully, but these errors were encountered: