From: John Scroggins <dataefx@earthlink.net>
To: Eric Peters <eric@peters.org>
Cc: SELinux@tycho.nsa.gov
Subject: Re: RBAC/Types Hierarchy
Date: Wed, 15 Aug 2001 18:17:35 -0700 [thread overview]
Message-ID: <3B7B1F2F.2276C50C@earthlink.net> (raw)
In-Reply-To: 00ec01c125e8$6aa2a950$020144c0@windows
Eric Peters wrote:
>
> 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)
snip>>
I think this may apply to all the people that were mentioned, but we
all have to start somewhere. The more we explore the possibilities, the
better the documentation. Projects are only as successful as their docs
represent, your questions may turn out to be a life saver, for someone
else.
snip>>
>
> 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.
snip>>
again you exhibit the ability to add value to the subject of WHAT to
document-- don't sell yourself short :) If you'd like, I can just tag
your name as a contributor -- I am excited to attempt this (along with
others), and I believe this whole project has substantial merit. If you
change your mind let me know
cheers
--JS
snip>>
>
> Look forward to reading your exploits,
>
> Eric
> >
> > --
> > 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.
next prev parent reply other threads:[~2001-08-16 1:17 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
2001-08-16 1:17 ` John Scroggins [this message]
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=3B7B1F2F.2276C50C@earthlink.net \
--to=dataefx@earthlink.net \
--cc=SELinux@tycho.nsa.gov \
--cc=eric@peters.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 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.