From: rsc@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: The problem with SSH2
Date: Fri, 26 Jan 2001 14:56:40 -0500 [thread overview]
Message-ID: <200101261956.OAA30860@smtp4.fas.harvard.edu> (raw)
it may just be the instances you have seen. i've spend a bit of time
with the draft documents; there is nothing intrinsic to its protocol
that necessiates those larded implementations.
no, but there's also nothing intrinsic to the
task at hand that requires such a larded
ad-hoc protocol. cpu(1) does everything
and more with just 9P and ssl. while you
might complain about ssl, the complexity
of the ssh protocol is not in the layer-level
encryption code. it's everything else.
you also might complain that 9P would be
too slow, but i tried it and found that the
small-packet latency was actually _less_
using 9P than using native ssh on the same
unix boxes for various networks.
we're stuck with ssh, but let's not delude
ourselves into thinking it's a good protocol.
(i'm talking about ssh1; ssh2 looks worse.)
russ
next reply other threads:[~2001-01-26 19:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-26 19:56 rsc [this message]
2001-01-26 20:46 ` Dan Cross
2001-01-29 13:40 ` David Rubin
2001-01-27 0:43 ` Boyd Roberts
2001-01-27 1:01 ` Boyd Roberts
2001-01-27 14:34 ` Markus Friedl
-- strict thread matches above, loose matches on Subject: below --
2001-01-27 2:34 rob pike
2001-01-27 2:37 ` Boyd Roberts
2001-01-27 2:13 dmr
2001-01-27 2:30 ` Boyd Roberts
2001-01-27 1:04 presotto
2001-01-01 15:37 rob pike
2001-01-01 15:43 ` Boyd Roberts
2001-01-02 8:27 ` Lyndon Nerenberg
2001-01-02 17:49 ` cLIeNUX user
2001-01-01 14:37 rob pike
2001-01-01 15:18 ` Markus Friedl
[not found] <20001231162642.A9783@folly>
2000-12-31 17:55 ` Jim Choate
2001-01-01 7:38 ` Boyd Roberts
2001-01-26 14:33 ` Ozan Yigit
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=200101261956.OAA30860@smtp4.fas.harvard.edu \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).