Re: [9fans] SSH-2.0

["Russ Cox" <rsc@plan9.bell-labs.com>]

[-- Attachment #1: Type: text/plain, Size: 387 bytes --]

ssh port forwarding would be easy to add.

it's not implemented on the server
because for non-plan9 clients, it's
hard to keep the access restricted to
the user who dialed.  at best forwarding
is restricted to the machine that user
is on, and at worst (the behavior of the
historical unix ssh clients) restricted to any machine
that is network-connected to the user's machine.

[-- Attachment #2: Type: message/rfc822, Size: 3833 bytes --]

[-- Attachment #2.1.1: Type: text/plain, Size: 92 bytes --]

A related question, has anyone looked at how hard it would be to add
ssh port forwarding?

[-- Attachment #2.1.2: Type: message/rfc822, Size: 2225 bytes --]

From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] SSH-2.0
Date: Wed, 5 Jun 2002 12:54:31 -0500
Message-ID: <82cf8099e6829c9a48da718a6a0c5834@plan9.bell-labs.com>

i had a go at ssh 2.0 four years ago.
it was terrible.  the protocol is much
larger, and the documentation at the time
didn't match the code, so i spent most
of my time adding print statements to the
ssh2 code to discover these discrepancies.

openssh may or may not be better code, but
i fear the documentation story will be the same.

i just don't care enough to try again,
at least not until a machine i care about
ends up running ssh2-only.

russ