Skip to content
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

Keychain Issue Under Leopard #1363

Closed
cyberduck opened this issue Nov 30, 2007 · 1 comment
Closed

Keychain Issue Under Leopard #1363

cyberduck opened this issue Nov 30, 2007 · 1 comment
Assignees
Milestone

Comments

@cyberduck
Copy link
Collaborator

20d24a6 created the issue

I've encountered a keychain issue that happens only with Cyberduck. I upgraded to Leopard, and when I double click a bookmark to connect, Cyber duck prompts me for the password, despite the fact that I've used that bookmark many times previously (as the password is stored in my keychain). If I go ahead and enter the password into the Cyberduck app and choose "save to keychain", then Cyberduck creates a new keychain entry, but the Keychain Access app doesn't like it because selecting that entry in the Keychain Access app results in an error:


An unexpected error has occurred that may cause Keychain Access to malfunction. You may want to quit the Keychain Access application.

Error: Invalid parameter not satisfying: aString != nil"

Opening the entry in the Keychain Access app reveals that there is no "where" field - i.e. no ftp URL. Cyberduck reads the entry just fine though (and connects) on subsequent launches. The Keychain Access app doesn't like the entry. If I add the ftp URL to the keychain entry manually, the Keychain Access app is happy and no longer gives an error, but Cyberduck can't read it and prompts me for my password when trying to connect.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

This is resolved in the latest nightly build. Please refer to #1354.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants