This is just a little tool I wrote to stop me from always having to add my new keys to all the machines that I ever want to remote into.
As a bonus, it pushes all the keys it knows about for a user to their linked GitHub account, too.
Thanks for sharing, I think this is a use case that most people end up reinventing at some point for their personal devices.
I’ve been using a (highly) simplified system whereby a cron job curls https://github.com/<user>.keys and overwrites the authorized_keys file.
This is crazy. I’m designing almost the exact same thing–right down to the UI choices–for the company I work for. We’re going to have a few more features but I would have gladly based my work on this and saved myself months of back-burner time.
And because it might come up, SSH key certificates are generally a MUCH better way to handle this problem but we have some non-technical users who can barely generate their own SSH to begin with, let alone figure out how to get it signed and put back in the right place.
we use hashicorp’s vault tool to handle SSH key signing. It makes it much more palatable for everyone.