Re: workarounds for Host param not canonicalizing?
From: Ryan Barrett (secureshell_at_ryanb.org)
Date: 05/22/05
- Previous message: Alexander Klimov: "Re: workarounds for Host param not canonicalizing?"
- In reply to: Alexander Klimov: "Re: workarounds for Host param not canonicalizing?"
- Next in thread: Alexander Klimov: "Re: workarounds for Host param not canonicalizing?"
- Reply: Alexander Klimov: "Re: workarounds for Host param not canonicalizing?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sun, 22 May 2005 02:10:43 -0700 (PDT) To: Alexander Klimov <alserkli@inbox.ru>
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.
-Ryan
-- http://ryan.barrett.name/
- Previous message: Alexander Klimov: "Re: workarounds for Host param not canonicalizing?"
- In reply to: Alexander Klimov: "Re: workarounds for Host param not canonicalizing?"
- Next in thread: Alexander Klimov: "Re: workarounds for Host param not canonicalizing?"
- Reply: Alexander Klimov: "Re: workarounds for Host param not canonicalizing?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|