From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: The problem with SSH2
Date: Fri, 26 Jan 2001 15:46:21 -0500 [thread overview]
Message-ID: <200101262046.PAA15533@augusta.math.psu.edu> (raw)
In-Reply-To: <200101261956.OAA30860@smtp4.fas.harvard.edu>
In article <200101261956.OAA30860@smtp4.fas.harvard.edu> you write:
>we're stuck with ssh, but let's not delude
>ourselves into thinking it's a good protocol.
Indeed.
It's that whole ``role model'' thing. It's hard for someone to design
a good protocol if they don't have good examples to work from. Same
thing with implementing software.
Most efforts these days are predisposed to poor implementations because
that's the only world that the people doing the implementations know
about; people *have* deluded themselves into thinking that these things
are ``good.'' But look at where this stuff is coming from: Solaris,
Linux, and Windows.
Coincidence? I think not.
Well designed systems help those that know about them, but aren't even
close to ubiquitous. Couple that with rabid dogmatism about the
systems they *do* know about, and the situation is grim.
- Dan C.
next prev parent reply other threads:[~2001-01-26 20:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-26 19:56 rsc
2001-01-26 20:46 ` Dan Cross [this message]
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=200101262046.PAA15533@augusta.math.psu.edu \
--to=cross@math.psu.edu \
--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).