Contents
How to SSH to servers internally by hostname?
You could use the CanonicalDomains option in your ssh config. Adding the following to your ssh config file will make ssh try to append domainname.com to any host that has at most 1 dot in its name : With this config ssh foo.eng will first try foo.eng.domainname.com, and fallback to foo.eng if the host cannot be found.
Where do I Save my SSH configuration file?
These can be saved to a configuration file that can be used to define per-host values. This can help keep the different connection options you use for each host separated and organized, and can keep you from having to provide extensive options on the command line whenever you need to connect.
When to use a different user name for SSH?
If you only want to ssh a few times, such as on a borrowed or shared computer, try: Specifies the user to log in as. This can be useful when a different user name is used on different machines. This saves the trouble of having to remember to give the user name on the command line.
Is it possible to connect to more than one host with OpenSSH?
Although the basics of connecting to a single host are often rather straight forward, this can become unwieldy and a much more complicated task when you begin working with a large number of remote systems. Fortunately, OpenSSH allows you to provide customized client-side connection options.
Can a host be un-hashed in SSH?
To your .ssh/config file but existing hosts won’t be un-hashed. Note that this has nothing at all to do with known_hosts hashing, contrary to what was stated above and the original question. If you wanted to autocomplete from known_hosts, then of course you would have to disable hashing, but that is strongly recommended against.
How to auto complete SSH my awe in Bash?
Then, you can just type ssh my-awe and it will be automagically completed. Again, this is even if you HashKnownHosts, which is highly recommended. (Note that bash completion needs to be enabled in your bash shell, and you need to specifically have those scripts installed as above for your distribution.)
Is there a bug in SSH completion in Ubuntu?
It seems that in Ubuntu the entries in ~/.ssh/known_hosts are hashed, so SSH completion cannot read them. This is a feature, not a bug. Even by adding HashKnownHosts no to ~/.ssh/config and /etc/ssh/ssh_config I was unable to prevent the host hashing.