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

Github host key should be updated ? #169

Closed
andreaslohre opened this issue Mar 24, 2023 · 2 comments · Fixed by #171
Closed

Github host key should be updated ? #169

andreaslohre opened this issue Mar 24, 2023 · 2 comments · Fixed by #171

Comments

@andreaslohre
Copy link

https://github.blog/2023-03-23-we-updated-our-rsa-ssh-host-key/

@na-jakobs
Copy link

Yup, hosts keys need to be updated right away :-| in the ssh-agent extension @mpdude

@mpdude
Copy link
Member

mpdude commented Mar 24, 2023

We have another issue (#108) with regards to host keys: On self-hosted runners which are not ephemeral the known_host file fills up with repeated entries, because every action run adds a new line with the same host keys.

Also, on those machines, the old key will still be in the known_hosts file.

IMHO this action should not be repsonsible for shipping SSH host keys, that's too much responsibility 😄 .

This section in the code is a leftover from early days when GitHub provided runners did not include SSH keys at all. For a long time already, GH takes care of placing their SSH keys in their runner images.

For self-hosted runners, those people setting up the runner should fetch and verify SSH keys themselves and put it into the known_hosts file.

I know this is a breaking change and is going to annoy users. But on the other hand, there is no better opportunity to drop this feature than with an emergency-style key revocation as today.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants