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

Passwords for private key not saved or read from keychain #10163

Closed
cyberduck opened this issue Dec 4, 2017 · 3 comments
Closed

Passwords for private key not saved or read from keychain #10163

cyberduck opened this issue Dec 4, 2017 · 3 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Dec 4, 2017

49e6e8c created the issue

Hi guys

Ever since latest update every time I click on a historic connection it asks me for password each time. I have select "keychain" in settings but it still doesnt remeber them

John


Attachments

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 6, 2017

@dkocher commented

I cannot reproduce the issue. Both opening a connection from a bookmark or from a recent item in the history tab will read the previously saved password from the keychain. Please provide exact steps to reproduce the issue and verify if the password entered can be found in your login keychain (Open Keychain Access.app)

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 19, 2018

a4f70d8 commented

This bug occur when you use SFTP certificate-based login, but does not occur when you use standard password login.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 9, 2018

@dkocher commented

I cannot reproduce this issue with a password protected private key.

@cyberduck cyberduck closed this Jul 13, 2018
@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
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants