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

Ignoring IdentityAgent from SSH config and -A CLI option #197

Open
inaneverb opened this issue Dec 22, 2023 · 0 comments
Open

Ignoring IdentityAgent from SSH config and -A CLI option #197

inaneverb opened this issue Dec 22, 2023 · 0 comments

Comments

@inaneverb
Copy link

inaneverb commented Dec 22, 2023

Affected Version

2.0.0
macOS 12.6.2 M1

Expected Behavior

Established SSH tunnel when no SSH keys are present as files in ~/.ssh, but has IdentityClient given by SSH config or -A flag in CLI.

Current Behavior

❯ mole start local --server=ard01 --destination=172.19.0.5:9000 --verbose -A '~/Library/Group Containers/2BUA8C4S2C.com.1password/t/agent.sock'
INFO[0000] instance identifier is d939cdad
DEBU[0000] using ssh config file from: ~/.ssh/config
ERRO[0000] error processing server options: error while reading key ~/.ssh/id_rsa: open ~/.ssh/id_rsa: no such file or directory
ERRO[0000] error creating tunnel                         error="error while reading key ~/.ssh/id_rsa: open ~/.ssh/id_rsa: no such file or directory" id=d939cdad
ERRO[0000] error starting mole                           error="error while reading key ~/.ssh/id_rsa: open ~/id_rsa: no such file or directory"

Steps to Reproduce

This is a part of SSH config (~/.ssh/config):

 33 Host ard01
 34         HostName xxx.xxx.xxx.xxx
 35         User deploy
 36
 37 Host *
 38         IdentityAgent "~/Library/Group Containers/2BUA8C4S2C.com.1password/t/agent.sock"

Observations:

  • IdentityAgent from SSH config doesn't work
  • -A option given to the CLI also doesn't work
  • Changing SSH_AUTH_SOCK env var right for mole also doesn't work

Details

This socket is a part of 1password SSH agent. There's details about it.

Having only this record in ~/.ssh/config all other applications are worked, including:

  • Executing directly ssh, git
  • Signing some things using GPG (also the same SSH keys are used), also using git

Am I missed something?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant