All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Eric Peters" <eric@peters.org>
To: "Stephen Smalley" <sds@tislabs.com>
Cc: <SELinux@tycho.nsa.gov>
Subject: Re: SE Linux II?
Date: Tue, 14 Aug 2001 18:12:36 -0700	[thread overview]
Message-ID: <001c01c12527$610738a0$020144c0@windows> (raw)
In-Reply-To: Pine.SOL.3.95.1010814081547.15893C-100000@clipper.gw.tislabs.com

Is there an anonymous CVS server available for download?

This question is a little out of blue I suppose, but i'm looking to
hopefully setup a system of directory permission access so I can have:

/home/user1
/home/user1/subuser1
/home/user1/subuser1/subuser1subuser1
/home/user1/subuser1/subuser1subuser2
/home/user1/subuser2

Type of heirachy where the user1 can access everything under his
/home/user1, subuser1 can access everything under his subuser1 home
directoyr, and subuser2 acccess to his directory and etc.

Would something like this be implemented out of the box with SELinux, or
could I potentially modify SELinux with relative ease to accomplish this
type of access.  basically I want the "controlling" account "user1" to be
able and access any "subuser1", "subuser2" files, where "subuser1" also has
access to his child accounts "subuser1subuser1", and "subuser1subuser2"
(user1 could also access these/his "children's"-"child" accounts)

Thanks I appreciate all your time,

Eric

----- Original Message -----
From: "Stephen Smalley" <sds@tislabs.com>
To: "Eric Peters" <eric@peters.org>
Cc: <SELinux@tycho.nsa.gov>
Sent: Tuesday, August 14, 2001 5:20 AM
Subject: Re: SE Linux II?


>
> On Mon, 13 Aug 2001, Eric Peters wrote:
>
> > Is there really any ETA on this release?
>
> I'm afraid that it is out of my hands.  We're currently blocked for
> bureaucratic reasons rather than technical ones.  I expect that it
> will occur within a week, but then again, it was supposed to happen
> before the end of the July.  We're now working off of the lsm-2001_08_12
> patch against kernel 2.4.8 from lsm.immunix.org.
>
> > hopefully at that point be more "upgradeable" without excessive kernel
> > recompiles correct?)
>
> Well, sort of.  The LSM kernel patch is itself still under
> rapid development.
>
> --
> Stephen D. Smalley, NAI Labs
> ssmalley@nai.com
>
>
>
>
>


--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2001-08-15  1:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-14  1:57 SE Linux II? Eric Peters
2001-08-14 12:20 ` Stephen Smalley
2001-08-15  1:12   ` Eric Peters [this message]
2001-08-15 12:35     ` Stephen Smalley
2001-08-15 16:29       ` Eric Peters
2001-08-15 17:38         ` Stephen Smalley
2001-08-15 17:39           ` Eric Peters
2001-08-15 17:39           ` Eric Peters
2001-08-15 19:38       ` RBAC/Types Hierarchy Eric Peters
2001-08-15 20:02         ` Stephen Smalley
2001-08-15 20:02           ` Eric Peters
2001-08-15 22:05         ` John Scroggins
2001-08-16  0:14           ` Eric Peters
2001-08-16  1:17             ` John Scroggins
2001-08-15 23:45               ` Dale Amon
     [not found]                 ` <3B7C110C.286A8E4C@earthlink.net>
     [not found]                   ` <20010816071759.C18183@vnl.com>
2001-08-16 19:44                     ` John Scroggins

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='001c01c12527$610738a0$020144c0@windows' \
    --to=eric@peters.org \
    --cc=SELinux@tycho.nsa.gov \
    --cc=sds@tislabs.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.