From: G. David Butler gdb@dbSystems.com
Subject: [9fans] The user 'none'
Date: Wed, 1 Oct 1997 10:33:17 -0500 [thread overview]
Message-ID: <19971001153317.sRquz7LgfQNSCnxXHUkhsUIZt9VAogHuajs2hVHDV0U@z> (raw)
Russ from rsc@plan9.bell-labs.com suggested a different
algorithm. Instead of:
...
if none and write access requested
not
if ingroup and group is allowed requested access
ok
else
not
...
Try
...
if ingroup
if not none and group is allowed requested access OR
if none and *other* is allowed requested access
ok
else
not
...
This says that if none is a member of a group and that group
has allowed others access, than none gets access too.
Better?
David Butler
gdb@dbSystems.com
next reply other threads:[~1997-10-01 15:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-01 15:33 G.David [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-10-01 14:25 rsc
1997-10-01 13:36 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=19971001153317.sRquz7LgfQNSCnxXHUkhsUIZt9VAogHuajs2hVHDV0U@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).