2 ms·
Users of github-keygen [1] might be affected. Please check the public key recorded in ~/.ssh/known_host_github. Note that github-keygen stores the ssh-ed25519
by dolmen 4y ago
Users of github-keygen [1] might be affected. Please check the public key recorded in ~/.ssh/known_host_github.
Note that github-keygen stores the ssh-ed25519 key since release 1.306 in June 2022. You can check by yourself:
cat ~/.ssh/known_hosts_github
If you are affected, just run github-keygen again to regenerate your SSH configuration:
curl --silent https://raw.githubusercontent.com/dolmen/github-keygen/release/github-keygen | perl
Disclaimer: I am the author and maintainer of github-keygen
[1]: https://github.com/dolmen/github-keygen/ https://github.com/dolmen/github-keygen/
- dolmen 4y agoNote that the use of curl for the upgrade is on purpose: if the user had a old copy of github-keygen made with `git clone` and the remote is configured using SSH, a `git remote update && git rebase` would not work because of the revoked SSH key. So, in this case, I consider that curl over https is safer as long as your curl version is recent and your local repository of TLS certificiates is up to date.