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: Tue, 18 Dec 2001 12:59:34 -0500 (EST)	[thread overview]
Message-ID: <1008698374.3c1f8406aded5@mail.outstep.com> (raw)
In-Reply-To: <Pine.GSO.4.33.0112181247180.4844-100000@raven>

Since I would like to modify the original files as little a possible then it 
sounds to me like Option 1 would be be the best direction and I can usr the 
user_t (user.te) as a template for this new user domain.

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?

Cheers,
Lonnie

Quoting Stephen Smalley <sds@tislabs.com>:

> 
> On Tue, 18 Dec 2001 lonnie@outstep.com wrote:
> 
> > Instead of modifying the user.te and every.te for our project, I think
> that it
> > might be better if I simple create a new test domain and place a
> "test" user in
> > that domain.
> 
> The rules in every.te are applied to every domain (or, to be more
> specific, to every type with the "domain" type attribute).  So if you
> create a test domain, these rules will also be applied to it unless
> you
> either 1) omit the "domain" type attribute from its declaration or 2)
> change every.te to exclude your test domain.
> 
> Option #1 will violate one of the assertions in the example policy, so
> you
> will have to remove that assertion from assert.te if you follow that
> route.  It will also require some additional rules for your test
> domain
> that are normally automatically picked up using the "domain"
> attribute,
> e.g. allowing init and the system administrator to kill the domain.
> 
> Option #2 requires you to edit every.te, but allows you to leave the
> assertions alone and lets you pick up the other rules automatically.
> If you name your new domain "testdomain", then you can do something
> like:
> 	sed "s/domain/~testdomain/g" every.te > newevery.te
> 	mv newevery.te every.te
> to create an every.te file that excludes your test domain.
> 
> > Would this be correct? If so then couls someone please help me to
> figure out
> > how to set up a simple domain from which to begin this process?
> 
> There are plenty of examples of domains in the current policy; use one
> of
> them as a starting point.  The most obvious one is the user_t domain
> that
> is currently used for ordinary users.  This is defined in
> domains/user/user.te.
> 
> --
> 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.

  reply	other threads:[~2001-12-18 17:59 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 [this message]
2001-12-18 18:29     ` Stephen Smalley
2001-12-18 19:43       ` lonnie
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=1008698374.3c1f8406aded5@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.