From: dpx@acl.lanl.gov
To: rsc@plan9.bell-labs.com, 9fans@cse.psu.edu
Subject: Re: [9fans] SSH-2.0
Date: Wed, 5 Jun 2002 12:32:47 +0000 [thread overview]
Message-ID: <2f3ae550142f67616f622405208c46e9@acl.lanl.gov> (raw)
[-- Attachment #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: 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
next reply other threads:[~2002-06-05 12:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-05 12:32 dpx [this message]
2002-06-05 17:13 anothy
2002-06-05 17:54 Russ Cox
2002-06-05 19:31 Russ Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2f3ae550142f67616f622405208c46e9@acl.lanl.gov \
--to=dpx@acl.lanl.gov \
--cc=9fans@cse.psu.edu \
--cc=rsc@plan9.bell-labs.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).