9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: G. David Butler gdb@dbSystems.com
Subject: [9fans] The user 'none'
Date: Wed,  1 Oct 1997 08:36:46 -0500	[thread overview]
Message-ID: <19971001133646.Whb5lbqInlSyXmoALhLuxJLlgTKTEujOXoRpnoFgPMo@z> (raw)

Someone previously mentioned that the user 'none' should
be handled differently for permissions.  After giving it
some thought I agree.

Just think about it, anybody that can route packets to your
file server can connect to it by using a Plan9 floppy and
using 'none'!  On a normal server, if other can read or write
a file, so can 'none'!  Even on old *nix I would never allow
a user access to my system without some kind of password.

So the question becomes, do we remove 'none's special status
(login without a password) or do we religate him to a 4th class
citizen.  The idea is that 'none' is *not* a member of the
"group" other, as was suggested.

None would then have to be explicitly mentioned as a member of
a group to get access to any files he doesn't own.  Since that
is how users are granted privs to update system files (user
"joe" is a member of group sys that has no group leader so he
can maintain the system files and the sys files have perms 775
so other users can get to them) none has to be denied write
access to all files except those that he owns.

The algorithm looks like:

if owner and owner is allowed requested access
	ok
else
	not

if none and write access requested
	not

if ingroup and group is allowed requested access
	ok
else
	not

if not none and other is allowed requested access
	ok
else
	not

Comments?

David Butler
gdb@dbSystems.com




             reply	other threads:[~1997-10-01 13:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-10-01 13:36 G.David [this message]
1997-10-01 14:25 rsc
1997-10-01 15:33 G.David

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=19971001133646.Whb5lbqInlSyXmoALhLuxJLlgTKTEujOXoRpnoFgPMo@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).