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

Tries to unlock keychain on every upload #3336

Closed
cyberduck opened this issue Jul 16, 2009 · 1 comment
Closed

Tries to unlock keychain on every upload #3336

cyberduck opened this issue Jul 16, 2009 · 1 comment

Comments

@cyberduck
Copy link
Collaborator

4bda9d1 created the issue

The password for one of my SFTP accounts is stored in a locked keychain. (In Keychain Access, it has "Lock after 1 minute of inactivity" selected.)

So I expect that the first time I connect to the site, I will be asked to unlock the Keychain so that Cyberduck can fetch the password.

However, my problem is that every time I upload a file,
I'm presented with a dialog

Cyberduck wants to use your confidential information stored in "shell.sonic.net" in your keychain.  Do you want to allow access to this item?  Always Allow / Deny / Allow.

Not only that, but "Transfers" window of Cyberduck, I see that "Login successful" has already been reported.

  • First problem: Why am I being asked to re-fetch my password from the keychain?
  • Second problem: How can login be successful if the password hasn't been fetched?

I click "Allow". The upload proceeds. But next time I attempt the same operation, I the same thing happens.

What I would like to happen:

I'm asked for my keychain password once, Cyberduck fetches the SFTP password, and the password is internally maintained for as long as the session is open, and I am never prompted for the password again.

Version 3.2.1 build 4923 (though it's been this way for a long time through many versions.)


Attachments

@cyberduck
Copy link
Collaborator Author

@dkocher commented

This is a duplicate of #2878 and has been fixed in 3.3.1.

@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