From: Nick <nagray@austin.rr.com>
To: SE Linux <selinux@tycho.nsa.gov>
Subject:
Date: Tue, 25 Nov 2003 22:52:17 -0600 [thread overview]
Message-ID: <1069822336.3447.1234.camel@hawaii> (raw)
Steve et Al.
Once the initial load has been done and the policy is in place, I should
be able to remove the development dirs (selinux-usr and linux-2.4) and
the policy source (/etc/security/selinux/src) from from my pseudo
production box and build new policies on my development server from the
/etc/security/selinux/src directory which I will then propagate over to
the system production system.
What about the file contexts, I didn't see these in the policy
directory?
I am working on several things and moving pretty fast so I may have
missed it.
I am going to have to create a /tcb directory and root all trusted code
there (policy, file contexts, binaries). I have been directed to move in
the direction of CMW. What are your thoughts on this.
Nick Gray
--
This message was distributed to subscribers of the selinux mailing 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 reply other threads:[~2003-11-26 4:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 4:52 Nick [this message]
2003-11-26 13:29 ` Stephen Smalley
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=1069822336.3447.1234.camel@hawaii \
--to=nagray@austin.rr.com \
--cc=selinux@tycho.nsa.gov \
/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.