From: Linda Knippers <linda.knippers@hp.com>
To: Joshua Brindle <jbrindle@tresys.com>
Cc: russell@coker.com.au, James Antill <jantill@redhat.com>,
selinux@tycho.nsa.gov
Subject: Re: User home directory creation with useradd (rhbz#217441)
Date: Sat, 02 Dec 2006 14:21:24 -0500 [thread overview]
Message-ID: <4571D234.5000207@hp.com> (raw)
In-Reply-To: <6FE441CD9F0C0C479F2D88F959B015885C821F@exchange.columbia.tresys.com>
>>> The sys-admin is wanting to create an entry for a user who
>>> can login. They don't want to think about creating a home
>>> directory, creating a group, a user, a home directory, a SE
>>> Linux user, and a SE Linux login mapping entry.
>>>
>
>
> Doesn't matter, semanage doesn't need any more feature creep than it has
> right now.
I don't want more stuff in semanage. We should be able to do it from
useradd, and from one role. Right now its a multi step operation and
we can't run useradd and semanage from the same role. Only sysadm_r
can run useradd and only secadm_r can run semanage with the current
MLS policy.
I've also noticed that only secadm_r can change the selinux context
of a file (makes sense) but secadm_r can't change the mode bits of
the same file, only sysadm_r can. That doesn't make sense to me.
I don't know if that's a bug, a feature or a configuration problem
on my system (and is somewhat off-topic) but its another example of
illogical behavior. Seems like secadm_r can do SELinux things but
not other security administration unrelated to SELinux, and that
makes SELinux look like a wart rather than an integrated feature.
Ok, here's another example. secadm_r can manage policy but can't
'touch /.autorelabel', only sysadm_r can do that.
-- ljk
--
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:[~2006-12-04 16:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 20:08 User home directory creation with useradd (rhbz#217441) James Antill
2006-12-01 20:22 ` Karl MacMillan
2006-12-04 2:39 ` David O'Brien
2006-12-04 13:49 ` Karl MacMillan
2006-12-04 23:38 ` David O'Brien
2006-12-01 20:47 ` Linda Knippers
2006-12-02 0:21 ` Russell Coker
2006-12-02 3:20 ` Joshua Brindle
2006-12-02 4:27 ` Russell Coker
2006-12-02 5:00 ` Joshua Brindle
2006-12-02 19:21 ` Linda Knippers [this message]
2006-12-02 19:29 ` Joshua Brindle
2006-12-05 8:42 ` Russell Coker
2006-12-02 23:08 ` Russell Coker
2006-12-04 17:43 ` Casey Schaufler
2006-12-04 18:10 ` Karl MacMillan
2006-12-04 19:34 ` Casey Schaufler
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=4571D234.5000207@hp.com \
--to=linda.knippers@hp.com \
--cc=jantill@redhat.com \
--cc=jbrindle@tresys.com \
--cc=russell@coker.com.au \
--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.