From: Debian User <rogelio@evoworks.evoserve.com>
To: selinux@tycho.nsa.gov
Subject: uclibc and selinux
Date: Fri, 14 Jun 2002 14:22:15 +0800 [thread overview]
Message-ID: <3D098B97.7030903@evoworks.evoserve.com> (raw)
Works very well. Are there legal problems if I merge libsecure into
uclibc? Its easier incorporating selinux into embedded linux.
How about incremental policy updates? So the policy does not have to
contain all possible policies needed in a system?
Also whats the best way to isolate users from each other when the passwd
file contains only "root" and "user" accounts?
--
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 reply other threads:[~2002-06-14 6:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-14 6:22 Debian User [this message]
2002-06-14 13:57 ` What is the story on patents and SELinux? Robert Hartley
2002-06-14 16:52 ` Russell Coker
[not found] ` <20020614153011.43908d6c.fw@fwsystems.com>
2002-06-14 20:27 ` Russell Coker
2002-06-14 21:27 ` richard offer
2002-06-14 18:55 ` Going OT (was Re: What is the story on patents and SELinux?) James Griffin
2002-06-20 14:57 ` uclibc and selinux Stephen Smalley
2002-06-20 19:53 ` Russell Coker
2002-06-20 21:58 ` Admissions Office
2002-06-21 11:11 ` 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=3D098B97.7030903@evoworks.evoserve.com \
--to=rogelio@evoworks.evoserve.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.