Re: SSH Option files using hashes instead of hostnames?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 28 Jun 2010, Dan Mahoney, System Admin wrote:
> 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


[Index of Archives]     [Open SSH Unix Development]     [Fedora Users]     [Fedora Desktop]     [Yosemite Backpacking]     [KDE Users]     [Gnome Users]

  Powered by Linux