Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Secure-Shell
[Top] [All Lists]

Re: workarounds for Host param not canonicalizing?

Subject: Re: workarounds for Host param not canonicalizing?
Date: Sun, 22 May 2005 02:10:43 -0700 (PDT)
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/

<Prev in Thread] Current Thread [Next in Thread>