From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: permissions idea (Re: [9fans] on the topic of viruses)
Date: Tue, 2 Oct 2001 11:37:09 -0400 [thread overview]
Message-ID: <20011002153721.A089919A34@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 203 bytes --]
Create two groups:
friends
acquaintances
then create the file
> file
chgrp -o friends file
chgrp acquaintances file
chmod 640 file
Make yourself the leader of friends and acquaintances.
[-- Attachment #2: Type: message/rfc822, Size: 2223 bytes --]
From: Matthew Hannigan <mlh@zip.com.au>
To: 9fans@cse.psu.edu
Subject: Re: permissions idea (Re: [9fans] on the topic of viruses)
Date: Tue, 02 Oct 2001 17:11:08 +0200
Message-ID: <3BB9D90C.C27A64E3@zip.com.au>
"Douglas A. Gwyn" wrote:
>
> Matthew Hannigan wrote:
> > ... perhaps we could have ...
>
> I don't think any scheme with fixed categories of trust
> can suffice for heavy-duty security. ...
Sure; I was just trying to figure out how
to get the mostest for the leastest.
I still think that my scheme of two groups
solves a large nr of cases.
How does plan9 solve the problem of someone
wanting to allow his close friends having write
access, acquaintances read access and others none?
I had a look at the man page but it seems to
have the same triple as unix. Or can the
owner be a group?
Regards,
-Matt
next reply other threads:[~2001-10-02 15:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-02 15:37 presotto [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-03 1:14 okamoto
2001-10-04 9:11 ` Douglas A. Gwyn
2001-09-28 1:06 [9fans] on the topic of viruses dmr
2001-09-28 9:58 ` Boyd Roberts
2001-10-01 16:13 ` permissions idea (Re: [9fans] on the topic of viruses) Matthew Hannigan
2001-10-01 16:18 ` Matthew Hannigan
2001-10-02 8:34 ` Douglas A. Gwyn
2001-10-02 15:11 ` Matthew Hannigan
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=20011002153721.A089919A34@mail.cse.psu.edu \
--to=presotto@plan9.bell-labs.com \
--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).