authenticity of host 'github.com can't be established about devspace HOT 16 CLOSED

From https://trello.com/c/z5LrlWMy/275-spaces-work:

ssh-keyscan github.com >> ~/.ssh/known_hosts

from devspace.

Just a note - this error can happen if You forgot to add Your ssh key to the repo You are trying to communicate with :)

from devspace.

thank you that works ;-)

from devspace.

Just typing "yes".

from devspace.

From https://trello.com/c/z5LrlWMy/275-spaces-work:

ssh-keyscan github.com >> ~/.ssh/known_hosts

Your amazing man , you made my day , thanks a lot

from devspace.

From https://trello.com/c/z5LrlWMy/275-spaces-work:

ssh-keyscan github.com >> ~/.ssh/known_hosts

Thank you so much for this.
I've been haunted by the error for quite some time.

from devspace.

@joshmoore how is this any safer than just answering the prompt with yes?
Either way, we are trusting that there is absolutely no corruption in our connection to github.com, what this security feature is made to address I thought?

from devspace.

Hi @Aaron-Penn-Interactive,

Hmm.... sounds like there's something else going on here. By my count, you've ok'd the authenticity at last twice but it's still not asking for confirmation which is weird. The only thing I can think of off-hand is if there are different users/machines/contexts by which known_hosts somehow changes.

I will note that GitHub itself has improved there docs around this in case there's anything there that might help you:

https://docs.github.com/en/free-pro-team@latest/github/authenticating-to-github/testing-your-ssh-connection

~Josh

from devspace.

it works thanks bro

from devspace.

Thank you!

from devspace.

looks like too early enthusiasm. I started fresh devspace deployment and having the same problem now. Running manually

bash-4.1$ /home/slave/.local/bin/scc merge develop --no-ask --reset -S success-only --push develop/merge/trigger

doesn't ask me the above question but still failing

from devspace.

@joshmoore thank u, it work!

from devspace.

Hi @Xerus2000. You're right that ssh-keyscan github.com >> ~/.ssh/known_hosts isn't safer at all. What this issue doesn't make clear though is that @aleksandra-tarkowska was looking for an automated way to start a fresh docker container which hasn't yet been primed with a known_hosts yet, i.e. there is no prompt that we can answer. This is a workaround at best.

from devspace.

I've been having this problem, but it doesn't ask if I want to continue. It just hangs there. I ran the ssh-keyscan command and I see the entry in the known_hosts file, but I still get the authenticity error. Even restarted my computer to no avail.
I also tried the test: ssh -T [email protected] and got this output:

<name>@<machine> ios-sportsbook % ssh -T [email protected]
Warning: Permanently added the RSA host key for IP address '140.82.114.3' to the list of known hosts.
Hi <githubUser>! You've successfully authenticated, but GitHub does not provide shell access.

Tried my git clone, but still got the error: The authenticity of host 'github.com (140.82.114.3)' can't be established. And it never asks if I want to continue

from devspace.

ssh-keyscan github.com >> ~/.ssh/known_hosts just leads to another error

npm WARN prepare removing existing node_modules/ before installation
npm ERR! Error while executing:
npm ERR! /usr/bin/git ls-remote -h -t ssh://[email protected]/kleros/dispute-resolver-interface-contract.git
npm ERR! 
npm ERR! Warning: Permanently added the ECDSA host key for IP address '140.82.121.4' to the list of known hosts.
npm ERR! [email protected]: Permission denied (publickey).
npm ERR! fatal: Could not read from remote repository.
npm ERR! 
npm ERR! Please make sure you have the correct access rights
npm ERR! and the repository exists.
npm ERR! 
npm ERR! exited with error code: 128

Just run ssh [email protected] instead

from devspace.

Hi @mpalenov. Sounds like there's more involved in your case. For example, the ssh-keyscan github.com >> ~/.ssh/known_hosts should have prevented npm ERR! Warning: Permanently added the ECDSA host key for IP address '140.82.121.4' to the list of known hosts. Perhaps it was run as a separate user or in a separate context? Also the error npm ERR! [email protected]: Permission denied (publickey). most likely comes from a missing SSH key somewhere. But if you are in an interactive shell, you're right: "Just run ssh [email protected] instead" 👍

from devspace.