[BUG] Extension doesn't see custom ssh agent

[kobrineli]

Hi! I am using custom ssh agent, which is set in both ~/.ssh/config and SSH_AUTH_SOCK env variable.
But when I try to connect to database via SSH tunnel, I see that plugin tries to use a default ssh agent instead of the custom one, and thus the authentication doesn't pass.

Is there any option to provide concrete path to ssh agent sock in the extension?

[AlexEfnd]

Upvote!

I'm having exact same issue. Used to have a direct connection to DB and it worked fine, bought the extension for it. But right now the policy changed and I need to use ssh tunnel with a custom agent - yet I'm stuck with the same problem, extension doesn't seem to use the agent specified in ~/.ssh/config

System Info:
MacOS Sonoma 14.7

[kobrineli]

UPD. The agent is selected correctly, but the problem still exists.

When agent provides more than one key/cert, the plugin takes only the first one, tries to authenticate with it, and, if it fails, closes the connection instead of trying to authenticate with the other provided keys or certificates.

[kobrineli]

@cweijan

[cweijan]

Thanks for the feedback, I don't know enough about ssh agent, I will try to support it better. As for now, I can only promise that I will never steal your private key.

[kobrineli]

All the patch is just to try authenticate with all provided identities instead of just the first one.

[cweijan]

@kobrineli I tested it and found that the ssh-agent supports multiple private keys. Please tell me your private key type. Maybe the private key format is not supported.

[kobrineli]

@cweijan public key type is ecdsa-sha2-nistp256-cert-v01@openssh.com
I think this is mostly about public keys rather than private keys, 'cause agent doesn't give private keys themselves.

[kobrineli]

@cweijan
Hi! Are there any updates on this issue?

[cweijan]

Hi, in the latest version 8.1.3, it supports custom SSH Agent path and automatically reads the key path from ~/.ssh/config.

[kobrineli]

@cweijan
It appeared that agent is being used correctly, but underlying lib for SSH doesn't support using certificates.

[kobrineli]

mscdex/ssh2#1440

Here is fix for ssh2.

[cweijan]

Hi, since I failed to configure the "ecdsa-sha2-nistp256-cert-v01@openssh.com" certificate, I cannot adapt it. In the latest version 8.2.0, I added the native method, which will use the native ssh command to connect, but will not be able to use sftp.