From: James Antill <jantill@redhat.com>
To: selinux@tycho.nsa.gov
Subject: User home directory creation with useradd (rhbz#217441)
Date: Fri, 01 Dec 2006 15:08:11 -0500 [thread overview]
Message-ID: <1165003691.18588.103.camel@code.and.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
As some of you know, there's an open BZ about the fact that in a
strict/MLS environment useradd doesn't create the user's homedir with
the correct context[1].
The problem is that matchpathcon() needs semanage to have run, so we
know what SELinux user the unix user is associated with, but that runs
separately and after useradd. The four obvious solutions are:
1. Have an option for useradd to call semanage to add the selinux user,
and then do the restorecon.
2. Have semanage do the equivalent of a restorecon when doing an
add/modify (or just add) of SELinux user information.
3. Have some kind of wrapper that does:
i. useradd
ii. semanage
iii. restorecon
4. Document that you need to call the list of programs in #3.
Does anyone have comments on which of the above they like/hate?
[1] http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=217441
--
James Antill <jantill@redhat.com>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2006-12-01 20:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 20:08 James Antill [this message]
2006-12-01 20:22 ` User home directory creation with useradd (rhbz#217441) 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
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=1165003691.18588.103.camel@code.and.org \
--to=jantill@redhat.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.