-
-
Notifications
You must be signed in to change notification settings - Fork 299
Regression 7.0.2 - 7.1.0: SSH agent not working anymore #10800
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
Comments
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. |
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 |
The same happen on Mountain Duck 3.2.0. Someone can confirm? |
Replying to [comment:9 rainbow]:
We will have a fix in Mountain Duck 3.2.1. |
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. |
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.
The text was updated successfully, but these errors were encountered: