3 ms·

This is why I keep a ~/.ssh/config file. I store all the hosts and various connection parameters (uernames, alternate ports, keys, etc.) in that file. Would th

This is why I keep a ~/.ssh/config file. I store all the hosts and various connection parameters (uernames, alternate ports, keys, etc.) in that file. Would that work for you?

ghshephard 2mo ago
So, I have this which I use about once a day: vis () { vim ~/.ssh/config } But - we have around 250k hosts in about 42 datacenters, some of them going back 8+ years, built by different teams - not everything has been standardized - and : $ wc -l ~/.ssh/config 268 /home/shephard/.ssh/config has lots and lots of weird IP mappings to ssh-keys that is just gross, and not something I would want to expose others to (mostly because it changes a lot behind the scenes) So - from time to time, someone will say, "hey - the key that should be working in this datacenter/cluster isn't working, how do you get connected" - at which point I so a ssh -vvv and eyeball which one was accepted. Being able to ask ssh just to print it out - would be awesome.