-
Notifications
You must be signed in to change notification settings - Fork 296
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
[BUG] Extension doesn't see custom ssh agent #1393
Comments
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 System Info: |
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. |
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. |
All the patch is just to try authenticate with all provided identities instead of just the first one. |
@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. |
@cweijan public key type is |
@cweijan |
@cweijan |
Here is fix for ssh2. |
Hi! I am using custom ssh agent, which is set in both
~/.ssh/config
andSSH_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?
The text was updated successfully, but these errors were encountered: