Re: PuTTY + cluster + server fingerprints
- From: Jacob Nevins <jacobn@xxxxxxxxxxxxxxxxxxxxxx>
- Date: 11 Jan 2007 12:38:49 +0000 (GMT)
cartimus@xxxxxxxxx writes:
Jacob Nevins wrote:
Use the same host key for all hosts on the cluster.
Unfortunately we don't administer that cluster and that is unlikely to
be allowed, I can ask! I was trying to find a workaround on the client
side though PuTTY may in fact negate any attempt.
In that case, here's a grim hack that will allow you to get round such
issues with the current state of PuTTY:
- On the Proxy panel, set "Proxy type" to Telnet and "Telnet command"
to the empty string.
- Set "Proxy hostname" and port to the real hostname and port you want
to connect to.
- On the "Session" panel, set the hostname and port to the name you
want the host key to be stored under.
What this does: the proxy setup creates a "null proxy" where a TCP
connection to one hostname is used as a proxy for a connection to
another hostname. The hostname/port you configure on the Session panel
get used to decide where the SSH host key is stored / looked up, but are
otherwise ignored, so they don't even have to correspond to a real
hostname.
.
- Follow-Ups:
- Re: PuTTY + cluster + server fingerprints
- From: cartimus
- Re: PuTTY + cluster + server fingerprints
- References:
- PuTTY + cluster + server fingerprints
- From: cartimus
- Re: PuTTY + cluster + server fingerprints
- From: Jacob Nevins
- Re: PuTTY + cluster + server fingerprints
- From: cartimus
- PuTTY + cluster + server fingerprints
- Prev by Date: Re: SSH on CYGWIN bash permissions error
- Next by Date: Problems to use ssh over stunnel and proxyserver
- Previous by thread: Re: PuTTY + cluster + server fingerprints
- Next by thread: Re: PuTTY + cluster + server fingerprints
- Index(es):
Relevant Pages
|
|