From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: "Bush, Daniel" <Daniel.Bush@boeing.com>
Cc: SELinux <SELinux@tycho.nsa.gov>
Subject: Re: Policy compiler issues.
Date: Thu, 20 May 2004 05:42:06 +0000 [thread overview]
Message-ID: <20040520054206.GE24597@lkcl.net> (raw)
In-Reply-To: <E7E29FA7C732D146887C784B34AEF6A0044E3FD7@xch-ne-01.ne.nos.boeing.com>
On Wed, May 19, 2004 at 06:10:17PM -0400, Bush, Daniel wrote:
> Hi all,
> I've got what is probably a fairly stupid question, but I'll ask anyway:
> I'm trying to deploy SELInux in an embedded environment. Footprint space is tight, every kilobyte counts. The environment is also fairly dynamic, the users list and assigned roles can change fairly rapidly.
> It's my understanding that whenever the users' list changes (aside from default users)in a SELinux system, that the policy files and security labels need to be re-compiled. Is there any way around that? Can a user be assigned a set of (non-default user) roles without re-compiling the security system?
hello, yes: if you look at /etc/selinux/users, you will note this:
#
# user_u is a generic user identity for Linux users who have no
# SELinux user identity defined. The modified daemons will use
# this user identity in the security context if there is no matching
# SELinux user identity for a Linux user. If you do not want to
# permit any access to such users, then remove this entry.
#
user user_u roles { user_r ifdef(`user_canbe_sysadm', `sysadm_r
system_r') };
so, if you don't want users to be able to be sysadmins, then
edit tunable.te to exclude the user_canbe_sysadm ifdef.
la?
l.
--
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 prev parent reply other threads:[~2004-05-20 5:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 22:10 Policy compiler issues Bush, Daniel
2004-05-20 3:22 ` Russell Coker
2004-05-20 5:42 ` Luke Kenneth Casson Leighton [this message]
2004-05-20 12:20 ` Stephen Smalley
-- strict thread matches above, loose matches on Subject: below --
2004-05-20 15:54 Bush, Daniel
2004-05-20 16:21 ` Stephen Smalley
2004-05-20 17:32 ` Frank Mayer
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=20040520054206.GE24597@lkcl.net \
--to=lkcl@lkcl.net \
--cc=Daniel.Bush@boeing.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.