SSH suthentication problems thru (versus to) a given host

[Derek D. Martin]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

At some point hitherto, Michael O'Donnell hath spake thusly:
> The problem is that SSH apparently fails to distinguish
> between SSH connecting TO a system versus THRU a system;
> when I switch (between saying
[SNIP]
> Suggestions?

1. Turn off StrictHostKeyChecking (if it's on) and ignore the warning
message.

2. IIRC, SSH host keys are stored using either the IP address, or the
host name you used to connect.  If the machine has more than one host
name, you can use one to connect to it directly, and the other to
connect through it to the forward-connected host.  This will create
different host keys based on the different name.  Alternately, you
might be able to accomplish the same thing by using the IP address of
the host for one and the name for the other.

I haven't tried this in quite some time, but it used to work for me
when I was sshing from work to two different systems on my home
network...  This is prolly circa 2000 (and OpenSSH v2.something). It's
certainly possible that things have changed enough since then, or that
it may require more control over your host resolution situation that
you have, such that this won't work for you...  

- -- 
Derek D. Martin
http://www.pizzashack.org/
GPG Key ID: 0x81CFE75D

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9ng/tdjdlQoHP510RAuOIAJ96zZakyXXapRD0H6Ff3/2mS+uHgQCdHDjV
Wr8/yaNpmNFE5UfScpUbEfM=
=VCT0
-----END PGP SIGNATURE-----