|
|
Secure Shell
SSH Option files using hashes instead of hostnames? Jun 27 2010 09:08PM Dan Mahoney, System Admin (danm prime gushi org) (1 replies) Re: SSH Option files using hashes instead of hostnames? Jun 28 2010 05:02PM Greg Wooledge (wooledg eeg ccf org) (1 replies) Re: SSH Option files using hashes instead of hostnames? Jun 29 2010 01:32AM Dan Mahoney, System Admin (danm prime gushi org) (3 replies) Re: SSH Option files using hashes instead of hostnames? Jun 29 2010 12:05PM Greg Wooledge (wooledg eeg ccf org) (1 replies) Re: SSH Option files using hashes instead of hostnames? Jun 29 2010 06:01PM Dan Mahoney, System Admin (danm prime gushi org) (1 replies) Re: SSH Option files using hashes instead of hostnames? Jun 30 2010 07:12PM Robert Hajime Lanning (robert lanning gmail com) Re: SSH Option files using hashes instead of hostnames? Jun 29 2010 08:01AM Robert Hajime Lanning (robert lanning gmail com) |
|
Privacy Statement |
> Now, assume I have that file hashed, but sitting in my ~/.ssh/config file,
> I have:
>
> # Server in guam is on overloaded DSL link
> Host slowpoke
> HostName slowpoke.secure.server.ad.company.com
> ConnectTimeout 600
> User admin
>
> [...]
> But compare this with
>
> HostnameHash |1|JYh/HiqdBkaEKeg0KrS9cHncJRI=|Qc2hMsrOMpReJLyOxwmps3nnb0k=
> ConnectTimeout 600
> User admin
>
> (Assume that the lookup of the hash was done AFTER resolving the FQDN in
> dns, like I said).
There is no requirement that "Host" is a lookup-able name and thus in
general it is impossible to derive "HostName" from it. Moreover, you
can use different "Host" names for the same "HostName" server, e.g.,
to setup different forwardings or use different user names:
Host sa
HostName server.example.com
User admin
Host sd
HostName server.example.com
User dan
--
Regards,
ASK
[ reply ]