Re: Don't write to known_hosts
- From: "Richard E. Silverman" <res@xxxxxxxx>
- Date: 07 Nov 2006 13:51:47 -0500
"BC" == Bernard Chan <cbkihong@xxxxxxxxxxx> writes:
BC> Dear All,
BC> The system administrator at my workplace here has done something
BC> that gave me a great deal of mess every time I try to SSH login
BC> from Linux.
BC> He has made some kind of port forwarding on a gateway host to
BC> protect some internal hosts behind. To SSH access the various
BC> hosts behind, I am asked to SSH to the gateway host, and a set of
BC> ports have been set aside which map to port 22 for each server
BC> behind.
BC> I think you can guess what the problem is. Due to different keys
BC> of each host, every time I need to connect to another host through
BC> another port I always need to go to known_hosts on my desktop
BC> machine to remove the line corresponding to the gateway host,
BC> otherwise there will be a key mismatch error preventing me from
BC> logging in further.
BC> I think there ought to be better ways to handle this, but as a
BC> software developer instead of an admin I am not aware if better
BC> methods exist. Or, can we simply prevent the SSH client from
BC> writing to known_hosts?
BC> The machines (desktop and servers) are all Linux machines and are
BC> all using openssh. I'm pretty sure somebody may have experienced
BC> this in the past, but I can find nothing useful on the Web. Thank
BC> you.
BC> Regards, Bernard Chan.
BC> -- Posted via a free Usenet account from http://www.teranews.com
[~/.ssh/config]
host foo
hostname gateway
port 1
host bar
hostname gateway
port 2
....
--
Richard Silverman
res@xxxxxxxx
.
- Follow-Ups:
- Re: Don't write to known_hosts
- From: Darren Tucker
- Re: Don't write to known_hosts
- References:
- Don't write to known_hosts
- From: Bernard Chan
- Don't write to known_hosts
- Prev by Date: Re: Multiple sshd instances
- Next by Date: chroot SFTP ONLY
- Previous by thread: Don't write to known_hosts
- Next by thread: Re: Don't write to known_hosts
- Index(es):
Relevant Pages
|
|