All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Eric Peters" <eric@peters.org>
To: "John Scroggins" <dataefx@earthlink.net>
Cc: <SELinux@tycho.nsa.gov>
Subject: Re: RBAC/Types Hierarchy
Date: Wed, 15 Aug 2001 17:14:22 -0700	[thread overview]
Message-ID: <00ec01c125e8$6aa2a950$020144c0@windows> (raw)
In-Reply-To: 3B7AF215.7ED269BA@earthlink.net

I'm afraid I would be a poor addition to counsel others in the use of
SELinux as I myself am just learning to use it.  (Still hoping I can manage
the Hierarchy restrictions - else I'll see about implementing them with a
standard file based ACL)

I am more than interested in perusing anything you guys are writing however.
There is definately to some regard, a need for multiple example policy files
to be developed for different operating environments, which could be easily
modeled and adapted by users of SELinux.

Look forward to reading your exploits,

Eric

----- Original Message -----
From: "John Scroggins" <dataefx@earthlink.net>
To: "Eric Peters" <eric@peters.org>
Cc: <SELinux@tycho.nsa.gov>
Sent: Wednesday, August 15, 2001 3:05 PM
Subject: Re: RBAC/Types Hierarchy


> Eric Peters wrote:
> >
> > I'll try to push this on a new thread and keep it more "open" for anyone
on
> > the list to respond :)
>
> snip>
>
> Thanks this is a good subject to tackle.
>
> btw: My name is John Scroggins, and I recently joined the list, and
> asked if anyone was developing the documentation for admins and users..
> Mr. Smalley responded with a "feel free", so I have been assessing the
> whole situation and I have enlisted the help of several players:
>
> 1) system administrator with a major Linux company
> 2) A CTO from A local ISP
> 3) A Senior UNIX database architect
> 4) A lawyer who has security environs experience
> 5) myself -- Linux book author and technical writer
>
> I want to get a broad view of all the possible scenarios, this will help
> the community in the long run. Your questions are highly relevant to the
> assembling of these docs, the more questions are posed and answered, the
> more complete the documentation.
>
> Would you like to get involved with the documentation effort for this
> project?
>
> --JS
> snip>
>
>
>
> > 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.
>
> --
> 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.
>


--
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-16  0:14 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
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 [this message]
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='00ec01c125e8$6aa2a950$020144c0@windows' \
    --to=eric@peters.org \
    --cc=SELinux@tycho.nsa.gov \
    --cc=dataefx@earthlink.net \
    /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.