All configured authentication methods failed - w/ agent + key #309
Comments
|
According to your logs, the extension did attempt to authenticate with the agent's key, but got rejected by the server. Can you access your OpenSSH logs on the server and see if it mentions anything about the failed key authentication? Mapped stack trace |
SchoofsKelvin
added
bug
ssh-rsa is deprecated in recent openssh. |
|
It seems like this is mscdex/ssh2#989. :/ |
|
We'll have to wait until |
SchoofsKelvin
added
dependencies
|
Well, it's a Yubikey, so I don't think I can really convert - plus there's nothing really wrong with my key - it works against newer openssh servers just fine, when the ssh client does the right thing. AFAICT, the workaround is loosening what the server accepts to allow the deprecated 'ssh-rsa' that |
|
I might take a look into adding a flag to forcefully set the type to The extension currently still uses |
|
@SchoofsKelvin I'm having the issue, how can I solve this? |
|
@francoism90 The fastest/easiest way is probably modifying your server configuration to allow these kind of keys (see above and mscdex/ssh2#989). Otherwise it's waiting for me to upgrade the extension to |
|
I ran into this issue when evaluating the extension and attempting to connect to a remote ssh host. The remote ssh server used the default sshd_config which ships with the Alpine distribution. The extension failed to connect using an The extension successfully connected using an Both public key types were authorized on the remote ssh host. The @SchoofsKelvin For new adopters like me who attempt to connect using a |
|
I've actually upgraded the extension so it now uses |
|
As I've mentioned in the linked issue #375, OpenSSH 8.8+ deprecated The "best" solution would be waiting for mscdex/ssh2#989 to be solved (e.g. if the author accepts mscdex/ssh2#1200 or a variant), but it doesn't seem like that might happen soon. Worst case, I can stop using the (full) official release of Alternatively, after looking around a bit in the source code, I could pre-parse keys and pre-instantiate agents I pass to Realistically, I might just go with the patch method right now. I've upgraded my test server to have OpenSSH 8.8+ and am able to reproduce the issue, so I can also immediately verify if the patch works. |
SchoofsKelvin
removed
waiting
|
I've pushed a fix that should fix this. You can download the |
|
I've published a new version of the extension (v1.26.1) which includes this fix, so it's not necessary anymore to manually install the custom build to test it. If you still encounter this issue, comment on (and reopen) this issue. |
|
I am facing the same issue I have installed (downgraded ) to the version v1.26.0, and now it's working fine. The v1.26.1 is causing this. I have removed all senstive data from the log: Flag "OPENSSH-SHA1" enabled due to 'missing', including convertSha1 for publickey authentication |
|
Same for me. After upgrading to 1.26.1 i had "All configured authentication methods failed" error for all ssh configs. |
|
Same for me and downgrading to 1.26.0 works fine. |
|
Same too, downgrading to 1.26.0 have fixed my issue |
|
Having the same issue when using newly created AWS EC2 Instance launched with RSA key-pair. Solved issue by creating new ED25519 key-pair, and attaching the new key-pair to existing EC2 Instance. Here is a guide: "Add or remove a public key on your instance": https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/replacing-key-pair.html In short:
|
Hi.
I can't connect to a remote host with this extension, even though I can from the terminal.
Let's first sanity check in the terminal (in VSCode even):
My sshfs config:
results in:
The text was updated successfully, but these errors were encountered: