The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: Toby Thain <toby@telegraphics.com.au>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Who's behind the UNIX filesystem permission implementation
Date: Wed, 31 Jul 2019 12:18:08 -0500	[thread overview]
Message-ID: <CANCZdfoF08SaZX4-693cOXHT0JK=48iza-YPcHHPF-tU_pfR1A@mail.gmail.com> (raw)
In-Reply-To: <e28d95ae-5696-7479-d967-1b754aaa56b0@telegraphics.com.au>

[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]

On Wed, Jul 31, 2019, 12:09 PM Toby Thain <toby@telegraphics.com.au> wrote:

> On 2019-07-31 5:59 a.m., Stephan Han. wrote:
> > Hello Unix enthusiasts.
> >
> > I'd like to know who or the group of people behind implementing this
> > filesystem permission system.
> > Since we are using this system for nearly 40 years and it addresses all
> > the aspects of the permission matter without any hustle.
>
> It may not address "all aspects" since it has been necessary for some
> purposes to extend the permission model substantially over time, such as
> ACLs, SELinux, etc.
>

He did say they solved the problem without hassle. All those other things
introduced hassle.  :) There is also all the various capacity frameworks to
self limit what you are allowed to do as any easy to administer exploits...

Warner

--Toby
>
>
> > I'm inspired to know who/how came up with this theory?
> > Also if it derived from somewhere else or If there's an origin story
> > about this, it would be worth to share.
> >
> > Cheers.
> > Stephan
> >
> > --
> > No When
>
>

[-- Attachment #2: Type: text/html, Size: 1765 bytes --]

  reply	other threads:[~2019-07-31 17:18 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
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 [this message]
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='CANCZdfoF08SaZX4-693cOXHT0JK=48iza-YPcHHPF-tU_pfR1A@mail.gmail.com' \
    --to=imp@bsdimp.com \
    --cc=toby@telegraphics.com.au \
    --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).