MacOS version to use SSH_AUTH_SOCK for ssh-agent

[amochkin]

Hi, is there any way to make Cyberduck v9.1.1 use SSH_AUTH_SOCK env var for SFTP key auth? Even though docs state that SSH_AUTH_SOCK is being evaluated if ~/.ssh/config doesn't have appropriate IdentityAgent, my experience is that Cyberduck just ignores SSH_AUTH_SOCK env var.

[dkocher]

SSH_AUTH_SOCK will only be visible to Cyberduck when you open the application from a shell where you have exported the environment variable such as with.

open /Applications/Cyberduck.app

[dkocher]

The documentation from 1Password ¹ has an example to install a launch agent to make the environment variable available to applications opened without Terminal.app.

Footnotes

1. https://developer.1password.com/docs/ssh/agent/compatibility/#ssh-auth-sock ↩

[amochkin]

SSH_AUTH_SOCK will only be visible to Cyberduck when you open the application from a shell where you have exported the environment variable such as with.

open /Applications/Cyberduck.app

This method doesn't work. Cyberduck app still ignores SSH_AUTH_SOCK env var. Even though that I see SSH_AUTH_SOCK being available for the Cyberduck.app process (using ps eww <pid>).

[dkocher]

Any IdentityAgent configuration directive in ~/.ssh/config that matches the hostname will take precedence over the SSH_AUTH_SOCK environment variable.

[amochkin]

After struggling to make it work without too much hassle I switched to Transmit5 - works perfectly well.

[dkocher]

I have opened #16954 which might be related to SSH_AUTH_SOCK not getting picked up.