logging into port-forwarded ssh confuses certs
HORNE_at_PSFC.MIT.EDU
Date: 12/29/03
- Previous message: Rajesh: "ssh using plink.exe giving "Unable to open connection: gethostbyname :unknown error""
- Next in thread: Darren Tucker: "Re: logging into port-forwarded ssh confuses certs"
- Reply: Darren Tucker: "Re: logging into port-forwarded ssh confuses certs"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 29 DEC 2003 19:28:49 GMT
I use redir (http://sammy.net/~sammy/hacks/)
to map ssh ports from behind my firewall, onto
the firewall -- so I can log into the interior machine from outside,
via "ssh -p <port> my.firewall.com".
(redir works well.)
This causes confusion in the "known_hosts" file on the client side,
because the cert associated with
the interior machine doesn't match that of my.firewall.com.
Is there a Canonical fix to this problem? Or a hack?
Or maybe a kludge? I'd rather not use the same cert for
all the machines -- that would qualify maybe as a bandaid?
Thanks
Steve
- Previous message: Rajesh: "ssh using plink.exe giving "Unable to open connection: gethostbyname :unknown error""
- Next in thread: Darren Tucker: "Re: logging into port-forwarded ssh confuses certs"
- Reply: Darren Tucker: "Re: logging into port-forwarded ssh confuses certs"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]