Live data from Hacker News

A command line tool to manage your ssh connections

github.com

11–20 of 33 posts

Re: A command line tool to manage your ssh connections

#11
Is it really easier than just editing ~/.ssh/config? In the config, you can use wildcards for groups of servers

    Host *.whatever.net
       IdentityFile ~/.ssh/whatever-key
       ServerAliveInterval 10
       port 1022
and then add specific information and aliases per host

    Host someserver.whatever.net someserver ss
      Hostname someserver.whatever.net
      User spin

    Host otherserver.whatever.net otherserver os
      Hostname otherserver.whatever.net
      User dritf
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.

Re: A command line tool to manage your ssh connections

#12
post #6

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. Manage your SSH like a boss? Perhaps, but only in the pointy-haired can't-read-man-ssh_config boss sense of the word. For those that don't want to install a script and would prefer to understand the tools they already have try this: http://nerderati.com/2011/03/simplify-your-life-with…

There are a lot of tools like that for years.

like;

- managing /etc/hosts - managing crontab

It's just a preference to do it with a command line tool, or just doing it in the config with editor.

Re: A command line tool to manage your ssh connections

#13

Is it really easier than just editing ~/.ssh/config? In the config, you can use wildcards for groups of servers Host *.whatever.net IdentityFile ~/.ssh/whatever-key ServerAliveInterval 10 port 1022 and then add specific information and aliases per host Host someserver.whatever.net someserver ss Hostname someserver.whatever.net User spin Host otherserver.whatever.net otherserver os Hostname otherserver.whatever.net Us…

It seems like one of those situations where it is better to just learn the tool you're using instead of learning a tool to configure the tool you're using.

Re: A command line tool to manage your ssh connections

#15

Is it really easier than just editing ~/.ssh/config? In the config, you can use wildcards for groups of servers Host *.whatever.net IdentityFile ~/.ssh/whatever-key ServerAliveInterval 10 port 1022 and then add specific information and aliases per host Host someserver.whatever.net someserver ss Hostname someserver.whatever.net User spin Host otherserver.whatever.net otherserver os Hostname otherserver.whatever.net Us…

It's probably not much easier, but the tool is almost certainly less error-prone. I like to see this extended with a GUI, but it's a good start.

Re: A command line tool to manage your ssh connections

#16
post #3
post #2

more easy to write bash aliases like alias ssh-web="ssh username@host" and you take bash completion support

There is bash completion for ssh. Its included as part of the bash-completion package on most distributions of linux. Its got extremely good completion support for hostnames It has the added advantage of also auto-completing for scp.

SCP autocomplete is very useful indeed. Especially when using ControlMaster, then autocomplete is almost instantly.

Re: A command line tool to manage your ssh connections

#17

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. http://www.funtoo.org/wiki/Keychain

slightly exaggerated: by that logic only one password should also be enough.

Re: A command line tool to manage your ssh connections

#20

Is it really easier than just editing ~/.ssh/config? In the config, you can use wildcards for groups of servers Host *.whatever.net IdentityFile ~/.ssh/whatever-key ServerAliveInterval 10 port 1022 and then add specific information and aliases per host Host someserver.whatever.net someserver ss Hostname someserver.whatever.net User spin Host otherserver.whatever.net otherserver os Hostname otherserver.whatever.net Us…

It's probably not much easier, but the tool is almost certainly less error-prone. I like to see this extended with a GUI, but it's a good start.

I doubt it's less error-prone. SSH config files aren't particularly complicated, and if you get it wrong, it's easy enough to fix - just edit the file again.
Post reply on HN