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

Regression 7.0.2 - 7.1.0: SSH agent not working anymore #10800

Closed
cyberduck opened this issue Sep 12, 2019 · 9 comments
Closed

Regression 7.0.2 - 7.1.0: SSH agent not working anymore #10800

cyberduck opened this issue Sep 12, 2019 · 9 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Sep 12, 2019

96851d2 created the issue

I use SSH public key authentication in combination with a yubikey and this howto: https://evilmartians.com/chronicles/stick-with-security-yubikey-ssh-gnupg-macos

$SSH_AUTH_SOCK is set correctly and Cyberduck 7.0.2 uses my Yubikey. After I update to 7.1.0 public key authentication is broken.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 13, 2019

@dkocher commented

Relates to #10454. $SSH_AUTH_SOCK only ever worked when you would open Cyberduck from the command line.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 13, 2019

@dkocher commented

Duplicate for #10454.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 13, 2019

96851d2 commented

Sorry, this is not a duplicate of #10454.

I have read and understood #10454 before i opened this bug.

If you create plists according to https://evilmartians.com/chronicles/stick-with-security-yubikey-ssh-gnupg-macos cyberduck 7.0.2 communicates with gpg-agent through its socket if started from the dock.

Cyberduck 7.1.0 does not communicate with gpg-agent neither when started through CLI or the dock and asks for username/password although my ssh server does not support password authentication and uses public key only.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 13, 2019

26dba51 commented

I can confirm the problem on my Windows 10 PC. With Cyberduck 7.0.1, it does work fine, using the running gpg agent configured with enable-putty-support (PuTTY does work, too, of course). With the update to 7.1.0, Cyberduck is not able to connect to my SSH server anymore and asks for a password instead.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 20, 2019

@dkocher commented

In 4a27918.

@cyberduck cyberduck closed this Sep 20, 2019
@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 23, 2019

86ddfdb commented

The same happen on Mountain Duck 3.2.0. Someone can confirm?

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 23, 2019

@dkocher commented

Replying to [comment:9 rainbow]:

The same happen on Mountain Duck 3.2.0. Someone can confirm?

We will have a fix in Mountain Duck 3.2.1.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 14, 2019

f59ad7c commented

This is still not working as expected for me. Cyberduck is still not able to authenticate using a key agent. Other pagent-compatible tools work fine.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 21, 2020

@dkocher commented

Replying to [comment:11 oliversalzburg]:

This is still not working as expected for me. Cyberduck is still not able to authenticate using a key agent. Other pagent-compatible tools work fine.
In #11394.

@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