You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So like other issues have mentioned, if you look at your own ~/.ssh/known_hosts file on a local computer that has connected to the server you will see something like this:
1.2.3.404 ssh-rsa LONGKEYHERE
What you really want to do is take everything after the IP as that is being added on later. So the value will look like this:
ssh-rsa LONGKEYHERE
I think that is pretty confusing. What is the rationale for not simply letting the user put the ip in the key secret variable? To hit other hosts with the same key?
The text was updated successfully, but these errors were encountered:
diericx
changed the title
Public key input is misleading ssh_public_key input is misleading
Apr 26, 2023
I ran into these errors while trying to set up the connection
And
What this script does is appends the
host
value and thessh_public_key
value to a new line in theknown_hosts
file heredocker-deployment-action/docker-entrypoint.sh
Line 85 in 878e582
So like other issues have mentioned, if you look at your own
~/.ssh/known_hosts
file on a local computer that has connected to the server you will see something like this:What you really want to do is take everything after the IP as that is being added on later. So the value will look like this:
I think that is pretty confusing. What is the rationale for not simply letting the user put the ip in the key secret variable? To hit other hosts with the same key?
The text was updated successfully, but these errors were encountered: