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

Fails to connect to known host with ed25519 fingerprint #76

Closed
trevarj opened this issue Dec 26, 2022 · 3 comments
Closed

Fails to connect to known host with ed25519 fingerprint #76

trevarj opened this issue Dec 26, 2022 · 3 comments
Labels
bug Something isn't working inactive No discussion on issue in awhile old Issue is really old, so may no longer apply

Comments

@trevarj
Copy link

trevarj commented Dec 26, 2022

If you have already connected to a server over ssh and saved a ssh-ed25519 fingerprint in ~/.ssh/known_host then doing :DistantLaunch [host name] fails to read the fingerprint.

Failed (1): Failed to launch server
Caused by:
    Fatal: host verification: host key mismatch for ssh server 192.168.1.1:22.
    Got fingerprint SHA256:7Bekk1Nx0yOKspOjOHEw+RfeaC2K9NDg51BUoVZEWBI instead of expected value from known_hosts
    file ~/.ssh/known_hosts.

Tried using v0.2 branch

@chipsenkbeil chipsenkbeil added the bug Something isn't working label Dec 29, 2022
@chipsenkbeil
Copy link
Owner

Whoops, had a reply waiting for this and never sent it. Thanks for the port, @trevarj!

I've seen this happen and not sure why. My workaround was just to delete the entry from the known_host file and recreate it as part of :DistantLaunch.

You could try changing the backend that powers the ssh functionality by doing :DistantLaunch options="ssh.backend=libssh" and see if that helps.

@trevarj
Copy link
Author

trevarj commented Jan 5, 2023

My workaround was just to delete the entry from the known_host file and recreate it as part of :DistantLaunch

Yep, this is what I ended up doing too. It recreates with a ecdsa key, so my guess is the default ssh backend must be expecting only that.

@chipsenkbeil chipsenkbeil added inactive No discussion on issue in awhile old Issue is really old, so may no longer apply labels May 15, 2023
@chipsenkbeil
Copy link
Owner

Closing out as an outdated issue. There's a workaround included in this issue, and this may also get resolved with chipsenkbeil/distant#193 for distant.

Nothing else that can be done in the neovim plugin itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working inactive No discussion on issue in awhile old Issue is really old, so may no longer apply
Projects
None yet
Development

No branches or pull requests

2 participants