Re: Port Forwarding and Multiple SSH Servers - WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!
From: Darren Dunham (ddunham_at_redwood.taos.com)
Date: 11/30/04
- Next message: Bill Unruh: "Re: My Linux server got hacked last night -- please help!"
- Previous message: Job Eisses: "Re: Port Forwarding and Multiple SSH Servers - WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!"
- In reply to: Job Eisses: "Re: Port Forwarding and Multiple SSH Servers - WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!"
- Next in thread: Darren Tucker: "Re: Port Forwarding and Multiple SSH Servers - WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 30 Nov 2004 00:10:30 GMT
Job Eisses <jei@jei.homelinux.net> wrote:
> Gary wrote:
>>
>> Behind my firewall I have several SSH servers that I connect to with
>> something like:
>> ssh -p xx user@firewall_IP_address
>> ... but I still get the error message. My workaound is to remove the key
>> in known_hosts and then connect but I need to find a better solution.
>> Is there one?
> My workaround, a bit clumsy, is to use "ssh -F configfileX ..." with a
> different
> configfileX for each host, and in that configfileX a reference to a
> different known_hosts file for each host. I came across it when i wanted
> to ssh to many different hosts from a single server via a ssh gateway
> host, each getting its own local portnumber.
> Extending the current use of known_hosts with a portnumber field in each
> hostline might make this more elegant.
Until that happens, I would think you could specify individual hosts in
the ssh_config file, then give them a port number and a
UserKnownHostsFile specification. That way you wouldn't have to specify
the -F (or the -p or the other bits) on the command line.
-- Darren Dunham ddunham@taos.com Senior Technical Consultant TAOS http://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area < This line left intentionally blank to confuse you. >
- Next message: Bill Unruh: "Re: My Linux server got hacked last night -- please help!"
- Previous message: Job Eisses: "Re: Port Forwarding and Multiple SSH Servers - WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!"
- In reply to: Job Eisses: "Re: Port Forwarding and Multiple SSH Servers - WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!"
- Next in thread: Darren Tucker: "Re: Port Forwarding and Multiple SSH Servers - WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|