9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Scott Schwartz schwartz@galapagos.cse.psu.edu
Subject: religious wars
Date: Fri, 18 Aug 1995 18:51:23 -0400	[thread overview]
Message-ID: <19950818225123.YzfFAppLLfCFVAepSFUaQCVumvqCmh31t4qBz0LS3U4@z> (raw)

I agree with most of what Dave wrote; here's my 2¢.

| If one takes Vadim's argument to the extreme, he
| should eliminate passwords internally since he
| has adequate protection, trusts everyone
| internally, and plan 9 is just a toy system.
| We ran that way ourselves for years
| (till management started using Plan 9 and wanted
| something better to keep us from seeing
| their secret stuff).

Lots of things about the system, and unix before it, reflect this mode
of development.  Consider file permissions: user/group/other is
adequate in uncomplicated circumstances, but in the typical university
setting access control lists would make life much easier,
particularly because the people you trust with particular files or
directories varies so much and so dynamically.

Also, there's a difference between any-user and unauthenticated-person
that user none doesn't seem to capture.  Shipping the system with
telnetd allowing "none" to log in from anywhere strikes me as a
mistake.  Allowing anonymous 9p connections is worrysome too.  AFS does
better, since it lets you restrict what unauthenticated users are
allowed to look at (easy with ACLs).

| Out biggest fear is that this pressure will make
| passwords a default mechanism.  We'ld rather see
| people working on getting Unix and DOS to use 
| better security or making Plan 9 security
| tighter like adding expontial key exchange than
| to add options to Plan 9 to make it less secure.
| Just the ability to do passwords in the clear is
| the first step down a very steep slope.  Climbing
| back up again is real hard.  We have a chance for
| a system that never goes that route, why blow it.

I very strongly agree with this.  In the unix world most people (and
vendors) aggressively avoid kerberos, s/key, and other things that
would improve our lives.  Plan 9 is a rare and valuable example of
doing things better and easier.  When I show it off to visitors I
always point that out.







             reply	other threads:[~1995-08-18 22:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-08-18 22:51 Scott [this message]
  -- strict thread matches above, loose matches on Subject: below --
1995-08-19 18:24 Rich
1995-08-19  1:27 Paul
1995-08-18 21:35 Berry
1995-08-18 20:48 presotto
1995-08-18  8:51 Vadim

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=19950818225123.YzfFAppLLfCFVAepSFUaQCVumvqCmh31t4qBz0LS3U4@z \
    --to=9fans@9fans.net \
    /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).