From: lonnie@outstep.com
To: SELinux Mailing <SELinux@tycho.nsa.gov>
Subject: Re: setting up new test user domain?
Date: Tue, 18 Dec 2001 14:43:57 -0500 (EST) [thread overview]
Message-ID: <1008704637.3c1f9c7d11aff@mail.outstep.com> (raw)
In-Reply-To: <Pine.GSO.4.33.0112181324340.4844-100000@raven>
Well, I actually have opted to go with Option #2 and have:
1. made a directory domains/test
2. cp domains/users/users.te ../test/testuser.te
3. sed "s/domain/~test_user/g" every.te newevery.te
mv newevery.te every.te
I should now go and add "test_user_r" to the rbac and then modify the
testuser.te to reflect test_user_t
I think that these are the correct steps?
Also, is there a small tutorial on doing some of these basic things?
Best Regards,
Lonnie
Quoting Stephen Smalley <sds@tislabs.com>:
>
> On Tue, 18 Dec 2001 lonnie@outstep.com wrote:
>
> > Now then, after making the new domain, should I presume that I can
> simply use
> > the standard "adduser" to put a user in that domain, and also use
> the
> > standard "chown" to change the ownership of files to belong to the new
> domain?
>
> No. adduser hasn't been modified to be aware of SELinux, and chown
> only
> deals with the Linux user and group attributes. You need to define an
> entry for the new user and his authorized roles in policy/users and an
> entry for the new role and its authorized domain(s) in policy/rbac.
> To
> set the security context on the user's home directory, you can use the
> new 'chcon' program.
>
> --
> Stephen D. Smalley, NAI Labs
> ssmalley@nai.com
>
>
>
--
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 prev parent reply other threads:[~2001-12-18 19:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-18 17:01 setting up new test user domain? lonnie
2001-12-18 17:59 ` Stephen Smalley
2001-12-18 17:59 ` lonnie
2001-12-18 18:29 ` Stephen Smalley
2001-12-18 19:43 ` lonnie [this message]
2001-12-19 14:20 ` lonnie
2001-12-19 15:03 ` Stephen Smalley
2001-12-19 17:55 ` Gary Lowder
2001-12-19 19:45 ` Stephen Smalley
2001-12-19 21:08 ` lonnie
2001-12-19 18:05 ` Debian SE Linux ? Noah silva
2001-12-19 18:34 ` Stephen Smalley
2001-12-20 11:43 ` Russell Coker
2001-12-20 14:44 ` Stephen Smalley
2001-12-20 15:34 ` Noah silva
2001-12-20 15:46 ` Stephen Smalley
2001-12-20 16:01 ` Noah silva
2001-12-20 16:09 ` Stephen Smalley
2001-12-19 18:28 ` setting up new test user domain? lonnie
2001-12-19 19:36 ` Stephen Smalley
2001-12-19 21:01 ` lonnie
2001-12-19 21:54 ` Stephen Smalley
-- strict thread matches above, loose matches on Subject: below --
2001-12-19 19:18 Flood Randy Capt AFCA/TCAA
2001-12-20 11:54 ` 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=1008704637.3c1f9c7d11aff@mail.outstep.com \
--to=lonnie@outstep.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.