Re: Port Forwarding and Multiple SSH Servers - WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!
From: Richard E. Silverman (res_at_qoxp.net)
Date: 11/22/04
- Next message: nobody_at_nodomain.invalid: "Re: Tectia Server 4.0 and OpenSSH 3.6.1 compatibility"
- Previous message: Richard E. Silverman: "Re: Port Forwarding and Multiple SSH Servers - WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!"
- In reply to: Gary: "Port Forwarding and Multiple SSH Servers - WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!"
- Next in thread: Job Eisses: "Re: Port Forwarding and Multiple SSH Servers - WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 22 Nov 2004 10:43:01 -0500
> On the client system $HOME/.ssh/config I've put :
> Host firewall_IP_address
> StrictHostkeyChecking no
>
> but I still get the error message.
Yes, this is to be expected. StrictHostkeyChecking alters how SSH handles
the conflict; it does not prevent the conflict.
-- Richard Silverman res@qoxp.net
- Next message: nobody_at_nodomain.invalid: "Re: Tectia Server 4.0 and OpenSSH 3.6.1 compatibility"
- Previous message: Richard E. Silverman: "Re: Port Forwarding and Multiple SSH Servers - WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!"
- In reply to: Gary: "Port Forwarding and Multiple SSH Servers - WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!"
- Next in thread: Job Eisses: "Re: Port Forwarding and Multiple SSH Servers - WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|