Is this just me or managing ssh keys is still in 1990? I freelance for a few companies which means about 100 new lines in .ssh/config. How do you guys solve this?
My .ssh/config file is 4kb, it has 77 HostName entries, it's easily backed up (and if I lose it I wouldn't really cry about it) and it's easy to maintain (every once in a while I add another server).
I'm not saying that this scales to large teams of developers and hundreds or more servers, but at this scale I really see no problems.
Likewise. We have a couple of dozen servers, for multiple clients (we're a web agency).
Provided you're organized, document things properly, and have a standard set of SSH keys, the only annoying part is the 30 seconds it takes to create a new entry in .ssh/config (or whatever ssh client you use).
3 comments
[ 2.8 ms ] story [ 17.0 ms ] threadMy .ssh/config file is 4kb, it has 77 HostName entries, it's easily backed up (and if I lose it I wouldn't really cry about it) and it's easy to maintain (every once in a while I add another server).
I'm not saying that this scales to large teams of developers and hundreds or more servers, but at this scale I really see no problems.
Provided you're organized, document things properly, and have a standard set of SSH keys, the only annoying part is the 30 seconds it takes to create a new entry in .ssh/config (or whatever ssh client you use).