port forwarding trouble

[Darren Tucker]

On Wed, Aug 10, 2005 at 11:19:28AM +1000, Damien Miller wrote:
> On Tue, 9 Aug 2005, Darren Tucker wrote:
> >http://bugzilla.mindrot.org/show_bug.cgi?id=910
> >
> >Brief overview from patch description:
> >Implement port spec as per sshd(8) ListenAddress
> >
> >The following are valid hostname entries:
> >localhost
> >127.0.0.1
> >::1
> >localhost:222
> >127.0.0.1:222
> >[::1]:222
> >
> >The first 3 should remain backward compatible with older versions and
> >are still written if possible.  The syntax is compatible with the sshd(8)
> >ListenAddress option (uses the same parser).
> 
> How does this work with HashKnownHosts?

Same as the previous diff, ie as far as I can tell it works the same way
as described above, with or without HashKnownHosts, and with or without
a matching hashed known_hosts entry for the server in question.

If there's a hashed known_hosts entry for "foo", and you connect to "foo"
port 123 without a hostkeyalias then you'll get an unknown host key
warning, but the same is true without an unhashed entry.

-- 
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
    Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.