Re:whoarethey: Determine Who Can Log in to an SSH Server
by psanford on Tuesday January 10, 2023 @09:54PM
(#34334505)
github does support ssh certs, but only for its enterprise offering.
Re:whoarethey: Determine Who Can Log in to an SSH Server
by enasterosophes on Tuesday January 10, 2023 @09:56PM
(#34334520)
Interesting, thanks. I had a feeling the support was limited to host certs.
Re:whoarethey: Determine Who Can Log in to an SSH Server
by chasil on Wednesday January 11, 2023 @02:22AM
(#34335988)
In any case, "sed -i" can be used to add new keys, and remove old ones, from a set of ~/.ssh/authorized_keys files on a collection of hosts.
It is good to be aware of the contents of these allowed credentials, and sweep unused entries. This article has a script that automates the procedure:
https://www.linuxjournal.com/content/ssh-key-rotation-posix-...
* You want to present different identities to the world and don't want them being conflated, eg separate your github hobby projects from your employer organization.
* You are using ssh certificate authentication, which isn't supported by GitHub yet, but you might be using it for other things, and GitHub should hopefully support it in the future. Since this relies on the name of the cert file matching the private key filename (eg id_ed25519-cert.pub corresponding to id_ed25519), you can't afaik have different certs active for the one key. Personally, I deal with this by simply having different private keys for different purposes, to avoid cert collision.