Re: workarounds for Host param not canonicalizing?

• Previous message: Darren Tucker: "Re: OpenSSH & ChRoot"
• In reply to: Ryan Barrett: "Re: workarounds for Host param not canonicalizing?"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Date: Mon, 23 May 2005 09:57:17 +0300 (IDT)
To: Ryan Barrett <secureshell@ryanb.org>

On Sun, 22 May 2005, Ryan Barrett wrote:

> On Sun, 22 May 2005, Alexander Klimov wrote:
>
> > so you CAN use `Host *.foo.com'
>
> that only works if you type the fully qualified name on the command line.
> from your man page quote:
>
> > The host is the hostname argument given on the command line (that is,
> > the name is not converted to a canonicalized host name before matching).
>
> if you ssh between machines often, and your domain name is long, e.g.
> *.research.foobar.com, you won't want to type it out every time. you can,
> but usability-wise, it's not much of a win.

If you want to save typing you can use in ssh_config, say,

 Host www
 HostName a-realy-long-name-of-the-www-server-or-its-IP

and when

 ssh www

man ssh_config:

     HostName
           Specifies the real host name to log into. This can be
           used to specify nicknames or abbreviations for hosts.
           Default is the name given on the command line. Numeric
           IP addresses are also permitted (both on the command
           line and in HostName specifications).

And, of course, you can generate your ssh_config if you have a lot of
such pairs, e.g.,

perl -e 'print "Host $_\nHostName $_.my.domain\n" for qw(www ftp smtp)'

-- 
Regards,
ASK

• Previous message: Darren Tucker: "Re: OpenSSH & ChRoot"
• In reply to: Ryan Barrett: "Re: workarounds for Host param not canonicalizing?"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]