Re: Backup problems using ssh because of host identification to a NAT

From: Per Hedeland (per_at_hedeland.org)
Date: 11/22/05

  • Next message: dare_eagle_at_yahoo.com: "SSH unable to connect" 
    Date: Tue, 22 Nov 2005 22:45:53 +0000 (UTC)

    In article <XCHgf.126942$S4.107387@edtnps84> Pham Nuwen <none@none.com>
    writes:
    >
    >Because B & C are behind a single IP they are running on different
    >ports. (1022 & 2022 respectively) The keys are all setup correctly, and
    >I have tested that they work individually to allow A to connect to
    >either B or C. The problem is the known_hosts file. If I add B then I
    >can no longer connect to C, because it complains about the potential MiM
    >attack. If I add C to known_hosts then it complains if I try to connect
    >to B. I played with StrictHostKeyChecking in the ssh_config file, but
    >even set to no, it doesn't do what I need.

    This problem has been discussed here a number of times in the past, see
    e.g.
    http://groups.google.com/group/comp.security.ssh/msg/e9a23d1dbedc9379
    for a solution.

    --Per Hedeland
    per@hedeland.org

  • Next message: dare_eagle_at_yahoo.com: "SSH unable to connect"