All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Joshua Brindle" <JBrindle@snu.edu>
To: <russell@coker.com.au>, <SELinux@tycho.nsa.gov>,
	<mark.westerman@westcam.com>
Subject: RE: Security Enhanced Linux distro
Date: Fri, 15 Nov 2002 11:51:16 -0600	[thread overview]
Message-ID: <sdd4dfd3.043@atlas.snu.edu> (raw)

I'm in the process of trying to integrate SELinux into Gentoo linux, if
you don't know anything about it it's a source based distro with a very
cool package management system. It was originally based on BSD Ports,
but has since become a very full solution. It is dependancy based etc,
has USE keywords to tell what support you want compiled in. Basically if
a user has the SELinux USE keyword it'll patch the userland utils (with
dependancy on the policy compiler and selinux kernel). This live system
upgrade you mention, what is it about? I presume you mean the problem
with having unlabeled files on the filesystem for some amount of time.
In gentoo all apps install to a temp directory where the file list is
enumerated and logged before copying to the live filesystem, is there
any way for me to label these files while in the temp directory, so that
they are labeled when they are copied to the live filesystem and this
latency between installation and labeling isn't a problem?


Joshua Brindle
UNIX Administrator
Southern Nazarene University

--
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.

             reply	other threads:[~2002-11-15 17:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-15 17:51 Joshua Brindle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-15 12:54 Security Enhanced Linux distro Mark Westerman
2002-11-15 13:16 ` Russell Coker
2002-11-15 12:25 Mark Westerman
2002-11-15 12:32 ` Security Enhanced Linux distro Russell Coker

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=sdd4dfd3.043@atlas.snu.edu \
    --to=jbrindle@snu.edu \
    --cc=SELinux@tycho.nsa.gov \
    --cc=mark.westerman@westcam.com \
    --cc=russell@coker.com.au \
    /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.