This was originally in the Google Group, but Dave Kocher suggested: No, this is not intended – we actually tried to improve interoperability with different authentication schemes for SSH. Can you please open a ticket at https://trac.cyberduck.io/newticket
This essentially is preventing me from using CyberDuck, so definitely looking for a solution soonest. I'm assuming others are having this same issue.
Does CyberDuck no longer use pageant on Windows to store and access ssh-keys? For me at least, it is not since this last update to v6.3. However MountainDuck 2.1.0 seems to be working fine will all the same bookmarks, and is accessing pageant just fine (same time, same computer).
If this is not an intentional change, any ideas on troubleshooting? The 'Use Keychain' is checked in Prefs, but opening any bookmark shows the message in the screenshot, and the 'save password' is automatically checked. If I edit this example bookmark, the username is in fact there in the bookmark, but you can see it is not visible in the connection dialog. Here, if I uncheck the 'save password', and add my username, the login button does nothing.
Looking forward to some constructive assistance, because I'm stumped here.
I should note that CyberDuck 6.3 is working fine for me on Mac, but currently Windows 10 is my main platform so this is a blocker for me, and I'm assuming others. Please contact me for whatever other information or troubleshooting details I can provide.
I see no change in the behaviour -- Still get the 'No login credential could be found in the Keychain' message.
Just to be certain here. This is Windows 10 (v 1709 build 16299.19).
pageant v0.70 is running, and works fine for putty v0.70 and for MountainDuck v2.1.0 (8541)
CyberDuck shotcurt has not changed (in 1yr or more), and looks like in the previous screen shot, with 'username' set and ssh private key set to 'none', and this can be observed by ritght-click the shortcut and select 'edit'
however, double-click on the short cut (or right-click and select connect to server), brings up a dialog box where there is NO username or password populated, SSH key set to none, and the 'Save Password' option is selected in the bottom left. And CyberDuck cannot connect. I tried to UN-check 'save password', and also add username, but still login does nothing.
Is there any log that I can send you?
Any more screen shots?
Have a screen sharing meeting (I use Zoom.us) and show you?
Any old settings I could or should try to remove?
I will say in general that for several years, the integration from CyberDuck to pagaent has been hard to understand. I think there should be a very clear check-box in each shortcut for the CyberDuck in Windows that confirms that you want to use pagaent as the ssh key store. Currently, it is confusing how to set up this configuration.
And the new terminology in the dialog about 'Keychain' is something that can confuse Windows-only users (and even Windows and Mac users like me), because 'Keychain' seems like a Mac/Linux term. If ONLY pagaent is supported in Windows (versus say ssh-agent from git-bash), then the Windows dialogs should be more clear, and there should be a a positive config for this, rather than just what it seems like -- pagaent will work if you have it running, and no other way to connect is provided.
Or there should be a more complete discussion in documentation of what 'Keychain' really means in Windows ... what keys (for what types of connections) are stored and how to setup the shortcut to use that.
I know understood the issue that is when validating provided credentials. For authentication with the SSH agent we neither need password nor public key set in the bookmark as we will try to authenticate with all keys found in the SSH agent first. Fix in 6372027.