Seems like Github's move to SSH keys only is a good one. I suck at keeping my SSH keys organized and remembering what's what. How do you keep your SSH keys organized?<p>Do you make notes in the .ssh/config file?
Do you use another tool to keep track of it?
Is it a GUI tool or a TUI or CLI tool?
I use ssh key agent of keepassxc. This way only the public keys reside in the ~/.ssh and all the private keys can be made usable by unlocking my keepassxc db(and unusable on locking the same). Keepassxc stores the passphrases, additional notes if any for the keys.<p>With a properly configured gitconfig, .ssh/config I use different keys per domain(for different github accounts), different keys for different domains(ssh) and the like.
I use SSH Config app on Mac (included with SetApp) for managing config.<p>I also use 'Secure Agent' which generates the private key in the hardware secure element with unlocking via biometric (with fallback to password). <a href="https://secure-agent.lapanthere.com/" rel="nofollow">https://secure-agent.lapanthere.com/</a>
I just use a single ssh key everywhere. The private key never leaves my laptop. Once in a while, I might want to clone one of my repos on my raspberry pi, in which case I use ssh agent forwarding.
Are you gonna build something to solve this problem?<p>I’d be interested in collaborating if you are and would like a hand. I’ve had a domain name ready for this exact project for a couple years.
ssh keys are tied to a user/machine tuple. When I create a new user account or (re)build a machine I <i>always</i> generate new keys and <i>never</i> copy private keys anywhere.<p>If the machine is owned by me it will have a git repo with per-hostname branches that holds an authorized_keys file. It also has a script that symlinks dotfiles and merges authorized keys with .ssh/id_rsa.pub and the local authorized keys file.