Just to clarify, the thing you posted uses its own custom config file and has a built-in UI for managing that config. We will *NOT* be doing that. So will using the STANDARD ~/.ssh/config suffice for you?
We would simply parse that for all the names and then execute 'ssh <name>' in a new terminal window.
Just to clarify, the thing you posted uses its own custom config file and has a built-in UI for managing that config. We will *NOT* be doing that. So will using the STANDARD ~/.ssh/config suffice for you?
We would simply parse that for all the names and then execute 'ssh <name>' in a new terminal window.