All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hubert Chan <hubert@uhoreg.ca>
To: reiserfs-list@namesys.com
Subject: Re: Using fs views to isolate untrusted processes: I need an assistant architect in the USA for Phase I of a DARPA funded linux kernel project
Date: Mon, 02 Aug 2004 20:04:34 -0400	[thread overview]
Message-ID: <873c35nl2l.fsf@uhoreg.ca> (raw)
In-Reply-To: 410EBBD5.4080308@dgreaves.com

>>>>> "David" == David Greaves <david@dgreaves.com> writes:

David> It sounds like running exe's setgid (or addgid?) and then having acls.
David> But then the acls are not tied to the file objects, more appended
David> to the file acl list by 'pattern' according to the exe.

Possibly.  But, from my understanding of views, apache would not even
be able to see that /etc/passwd exists -- it is not just limited to not
being able to read it.  I don't think you can do that with acls, and
still allow apache to see some entries in /etc.

It also seems much easier to administer, since the permissions are tied
to the executable, rather than being tied to the file object.  (Say I
want to see what files apache can read as part of a security audit --
with acls, I would have to do a search over the whole filesystem.)

-- 
Hubert Chan <hubert@uhoreg.ca> - http://www.uhoreg.ca/
PGP/GnuPG key: 1024D/124B61FA
Fingerprint: 96C5 012F 5F74 A5F7 1FF7  5291 AF29 C719 124B 61FA
Key available at wwwkeys.pgp.net.   Encrypted e-mail preferred.


  reply	other threads:[~2004-08-03  0:04 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-02  1:20 Using fs views to isolate untrusted processes: I need an assistant architect in the USA for Phase I of a DARPA funded linux kernel project Hans Reiser
2004-08-02  9:12 ` Christian Mayrhuber
2004-08-02 17:29   ` Hubert Chan
2004-08-02 18:18     ` Hans Reiser
2004-08-02 19:02     ` Christian Mayrhuber
2004-08-02 19:55       ` Hans Reiser
2004-08-02 22:10     ` David Greaves
2004-08-03  0:04       ` Hubert Chan [this message]
2004-08-03  4:30         ` Matt Stegman
2004-08-03  8:30         ` David Greaves
2004-08-03 10:08         ` Pierre Etchemaite
2004-08-03 10:58 ` James Courtier-Dutton
2004-08-04  5:44   ` Hans Reiser
2004-08-25 20:25 ` Rik van Riel
2004-08-25 20:56   ` Tim Hockin
2004-08-25 21:23     ` Mike Waychison
2004-08-26  6:31       ` Hans Reiser
2004-08-26 13:59         ` Stephen Smalley
2004-08-25 23:19     ` Kyle Moffett
2004-08-26  0:16       ` Mike Waychison
2004-08-26  0:50         ` Kyle Moffett
2004-08-26  1:06           ` Chris Wright
2004-08-26  4:16             ` Kyle Moffett
2004-08-26  4:29               ` viro
2004-08-26  4:52                 ` Kyle Moffett
2004-08-26  5:01                   ` viro
2004-08-26  0:56         ` Chris Wright
2004-08-26  7:52         ` Hans Reiser
2004-08-26  8:48   ` Hans Reiser

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=873c35nl2l.fsf@uhoreg.ca \
    --to=hubert@uhoreg.ca \
    --cc=reiserfs-list@namesys.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.