Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!dayton!ems!umn-cs!randy
From: randy@umn-cs.UUCP (Randy Orrison)
Newsgroups: comp.unix.wizards
Subject: Re: GNU security, size
Message-ID: <2580@umn-cs.UUCP>
Date: Tue, 3-Nov-87 10:49:26 EST
Article-I.D.: umn-cs.2580
Posted: Tue Nov  3 10:49:26 1987
Date-Received: Sun, 8-Nov-87 10:48:39 EST
References: <7399@alice.UUCP>
Reply-To: randy@umn-cs.UUCP (Randy Orrison)
Organization: UofM Math Department
Lines: 28
Keywords: GNU security, size

In article <7399@alice.UUCP> wilber@alice.UUCP writes:
>What RMS could do without violating his security philosophy is provide
>the standard UNIX protection capabilites except with no passwords.
>That way anyone who wanted to could log in as root whenever there was a
>reason for it but normally the system would protect you from your own
>stupidity.

Or, he could implement standard UNIX protection capabilities as it is now,
except supply the default /etc/passwd with all the password fields blank.
And the default umask set to 0.

That way, he (and others with similar feelings) could have their zero security,
but others (with other needs) could change things...

I really doubt that RMS has any intention of getting rid of such 'security'
features as limitations on memory accesses.  What we need here is for RMS or
someone who knows him to let us know exactly what's going to be in GNU, so
we can start putting in requests for what we want.  (Does anyone know what's
going to be in GNU?  Does anyone know what's already in GNU?  for example,
how far along is the kernel?  Is there a kernel yet?)

Disclaimer:  If i had time, i'd help.  Maybe after I graduate and am only
working 40 hours a week, instead of 60~ between school and work.
-- 
Randy Orrison, University of Minnesota School of Mathematics
UUCP:	{ihnp4, seismo!rutgers!umnd-cs, sun}!umn-cs!randy
ARPA:	randy@ux.acss.umn.edu		 (Yes, these are three
BITNET:	randy@umnacca			 different machines)