4 ms·
ssh keys are tied to a user/machine tuple. When I create a new user account or (re)build a machine I always generate new keys and never copy private keys anywhe
by swiley 6y ago
ssh keys are tied to a user/machine tuple. When I create a new user account or (re)build a machine I always generate new keys and never copy private keys anywhere.
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.
- l00sed 6y agoI'm using SSH more and more, and this is all stuff I want to be able to do. I'd love to pass a specific bashrc and vimrc. I feel like it's hard to keep track of what's going on when I have 10 keypairs for git and remote servers. Is it bad practice to use more than one SSH keypair? Do you have some kind of dashboard that can provide more verbosity about what each one's for or how it's configured with tags or something...
- swiley 6y ago>Is it bad practice to use more than one SSH keypair? Not that I'm aware of. You could actually argue that it's bad practice to not have different keypairs for eg signing commits, authenticating to github, and using shell accounts on different services. Most people like me are just too lazy to do that, but you could use a `host: *.domain` line in your ssh config to do it.
- l00sed 6y agoI guess RSA ends with user@host, but I don't have a nice view to see that all at once...