From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <2f3ae550142f67616f622405208c46e9@acl.lanl.gov>
To: rsc@plan9.bell-labs.com, 9fans@cse.psu.edu
Subject: Re: [9fans] SSH-2.0
From: dpx@acl.lanl.gov
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="upas-jsmxspzovpxpqvpphaidzqmyie"
Date: Wed,  5 Jun 2002 12:32:47 +0000
Topicbox-Message-UUID: a67eb318-eaca-11e9-9e20-41e7f4b1d025

This is a multi-part message in MIME format.
--upas-jsmxspzovpxpqvpphaidzqmyie
Content-Disposition: inline
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

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

--upas-jsmxspzovpxpqvpphaidzqmyie
Content-Type: message/rfc822
Content-Disposition: inline

Received: from acl.lanl.gov ([128.165.147.1]) by acl.lanl.gov; Wed Jun  5 17:55:16 GMT 2002
Received: (qmail 1608227 invoked by uid 2345); 5 Jun 2002 11:55:16 -0600
Delivered-To: dpx@acl.lanl.gov
Received: (qmail 1633542 invoked from network); 5 Jun 2002 11:55:15 -0600
Received: from mailrelay2.lanl.gov (128.165.4.103)
  by acl.lanl.gov with SMTP; 5 Jun 2002 11:55:15 -0600
Received: from mailproxy1.lanl.gov (localhost.localdomain [127.0.0.1])
	by mailrelay2.lanl.gov (8.11.6/8.11.6/(ccn-5)) with ESMTP id g55HtFn12519;
	Wed, 5 Jun 2002 11:55:15 -0600
Received: from mail.cse.psu.edu (psuvax1.cse.psu.edu [130.203.4.6])
	by mailproxy1.lanl.gov (8.11.6/8.11.6/(ccn-5)) with ESMTP id g55HtEw27595;
	Wed, 5 Jun 2002 11:55:14 -0600
Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.30.6])
	by mail.cse.psu.edu (CSE Mail Server) with ESMTP
	id E732B19B41; Wed,  5 Jun 2002 13:55:07 -0400 (EDT)
Delivered-To: 9fans@cse.psu.edu
Received: from plan9.cs.bell-labs.com (closedmind.org [204.178.31.2])
	by mail.cse.psu.edu (CSE Mail Server) with SMTP id 2D22419B3B
	for <9fans@cse.psu.edu>; Wed,  5 Jun 2002 13:54:33 -0400 (EDT)
Message-ID: <82cf8099e6829c9a48da718a6a0c5834@plan9.bell-labs.com>
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] SSH-2.0
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Sender: 9fans-admin@cse.psu.edu
Errors-To: 9fans-admin@cse.psu.edu
X-BeenThere: 9fans@cse.psu.edu
X-Mailman-Version: 2.0.11
Precedence: bulk
Reply-To: 9fans@cse.psu.edu
List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu>
List-Archive: <https://lists.cse.psu.edu/archives/9fans/>
Date: Wed, 5 Jun 2002 12:54:31 -0500

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

--upas-jsmxspzovpxpqvpphaidzqmyie--