All of lore.kernel.org
 help / color / mirror / Atom feed
From: lonnie@outstep.com
To: SELinux Mailing <SELinux@tycho.nsa.gov>
Subject: Re: setting up new test user domain?
Date: Wed, 19 Dec 2001 09:20:30 -0500 (EST)	[thread overview]
Message-ID: <1008771630.3c20a22e1de4b@mail.outstep.com> (raw)
In-Reply-To: <Pine.GSO.4.33.0112181324340.4844-100000@raven>

Hi there,

I have made a copy of the user.te to be_user.te and have changes all instances 
of "user" ti "be_user" and changed the "domain" to "be_domain" inside 
be_user.te.

I have also added the be_user_r definition to the rbac file.

The las t thing that I have done was to "sed "s/domain/~be_domain/g" every.te > 
newevery.te and then copy it over.

the problem that I am getting now is an assertion error:

assertion fail: allow be_user_su_t be_user_t:process { transition } was granted

could you please tell me what these assertion errors mean and, in general, how 
to fix them?

Cheers,
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.
> 

--
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.

  parent reply	other threads:[~2001-12-19 14:20 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
2001-12-19 14:20       ` lonnie [this message]
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=1008771630.3c20a22e1de4b@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.