From: Arthur Krewat <krewat@kilonet.net>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Who's behind the UNIX filesystem permission implementation
Date: Wed, 31 Jul 2019 13:29:16 -0400 [thread overview]
Message-ID: <e3bcb400-8405-cc0f-7d2c-eb7019215e08@kilonet.net> (raw)
In-Reply-To: <CA+cCjXrWok5DR61hA0xKEodMfVyCUgNmsksTCjS6u6Aikf-0pw@mail.gmail.com>
On 7/31/2019 12:49 PM, Rodrigo G. López wrote:
> Multics had modes per file (https://multicians.org/fjcc4.html) but i
> don't know about the origins. the simpler approach of
> owner/group/other is a purely Unix creation and i would bet Ken
> Thompson is behind it all.
TOPS-10 had a 3 octal digit file protection code:
<xxx> - <Owner, Project, Everyone else> - Logins are PPNs - [Project,
Programmer] - So if I was [76,5], another user with [76,10] was in the
same project. Much like UNIX groups.
Owner Protection Codes
7*, 6* - You can execute, read, or change the protection code of the file.
5* - You have unlimited access to the file, except for renaming it.
4* - You have unlimited access to the file.
3 - You can execute, read, or change the protection code of the file.
2 - You have unlimited access to the file, except for renaming it.
1, 0 - You have unlimited access.
* The File Daemon is called on a protection failure on this file (my
memory is a little fuzzy on this, but I believe it allowed finer grained
protections).
Protection Codes for Fields 2 and 3
7 - The user cannot access the file.
6 - The user can only execute the file.
5 - The user can execute or read the file.
4 - The user can execute, read, or append to the file.
3 - The user can execute, read, append to, or update the file.
2 - The user can execute, read, append to, update, and write to the file.
1 - The user can execute, read, append to, update, write to, and rename
the file.
0 - Unlimited access, including changing the protection code of the file.
The name TOPS-10 was first used in 1970, but the monitor itself dates
back to 1964. I'm not sure when these protection codes came into being,
though.
next prev parent reply other threads:[~2019-07-31 17:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 9:59 Stephan Han.
2019-07-31 16:49 ` Rodrigo G. López
2019-07-31 17:29 ` Arthur Krewat [this message]
2019-07-31 17:58 ` Clem Cole
2019-07-31 18:03 ` Christopher Browne
2019-07-31 20:16 ` Arthur Krewat
2019-07-31 17:00 ` Toby Thain
2019-07-31 17:18 ` Warner Losh
2019-07-31 22:24 ` William Corcoran
2019-07-31 22:49 ` George Michaelson
2019-07-31 18:46 ` Grant Taylor via TUHS
2019-07-31 19:01 ` Clem Cole
2019-07-31 19:34 ` Ben Greenfield via TUHS
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=e3bcb400-8405-cc0f-7d2c-eb7019215e08@kilonet.net \
--to=krewat@kilonet.net \
--cc=tuhs@minnie.tuhs.org \
/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).