Is it really easier than just editing ~/.ssh/config? In the config, you can use wildcards for groups of servers<p><pre><code> Host *.whatever.net
IdentityFile ~/.ssh/whatever-key
ServerAliveInterval 10
port 1022
</code></pre>
and then add specific information and aliases per host<p><pre><code> Host someserver.whatever.net someserver ss
Hostname someserver.whatever.net
User spin
Host otherserver.whatever.net otherserver os
Hostname otherserver.whatever.net
User dritf
</code></pre>
Plus, since you probably edit it only once in a while, you don't need to remember the syntax and can simply base new additions on existing entries.
I hate to be snarky but having read through the code this really isn't a big thing. It's a tool for people that can't use .ssh/config.<p>Manage your SSH like a boss? Perhaps, but only in the pointy-haired can't-read-man-ssh_config boss sense of the word.<p>For those that don't want to install a script and would prefer to understand the tools they already have try this:<p><a href="http://nerderati.com/2011/03/simplify-your-life-with-an-ssh-config-file/" rel="nofollow">http://nerderati.com/2011/03/simplify-your-life-with-an-ssh-...</a>
I agree with the comments to just freakin edit your .ssh/config. But, it clearly states "SSH like a boss". The implication I take means "configure ssh for people who don't know how to use an editor, can't read man page, don't know where man pages are, and can't find/don't know about .ssh."<p>So, not for us. We can move along and be happy someone else is taking care of those people.
I've built a script that creates the config by querying EC2 for servers, this avoids having to pass around server names when new servers are created. Just run the script and every server is added.
When I saw the project name, the first thing I thought of was: <a href="https://github.com/nathanmarz/storm" rel="nofollow">https://github.com/nathanmarz/storm</a>
Very cool. I'd love to actually set this up with some scripts as a way to manage server migrations or new servers<p>I'm actually working on a web-based gui for managing ssh configs and I'm likely to switch to python and reuse some of this
In OS X, by pressing Cmd+Shift+K whilst in Terminal.app, you can save SSH, SFTP, FTP and telnet connections. Personally I don't use it but some people might prefer it.
If this could make key management significantly easier (e.g. no need to rely on the buggy GNOME keychain app) or make it easier to manage persistent connections (ControlMaster is trivial, but juggling dozens of connections and gracefully terminating/resuming them is not), maybe it would be genuinely useful.<p>For the time being, though, this just looks like a lightweight editor for ssh_config.
I can see this being useful if you have lots of keys and the server kicks you when you try too many of them, but in theory you really shouldn't need more than one key.<p><a href="http://www.funtoo.org/wiki/Keychain" rel="nofollow">http://www.funtoo.org/wiki/Keychain</a>