All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dominick Grift <domg472@gmail.com>
To: Cheyenne Solo <ayla.cheyenne@gmail.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
	selinux@tycho.nsa.gov, Daniel J Walsh <dwalsh@redhat.com>
Subject: Re: Base module, modules.conf
Date: Wed, 04 Feb 2009 22:53:31 +0100	[thread overview]
Message-ID: <1233784411.6488.28.camel@localhost.localdomain> (raw)
In-Reply-To: <5ab9a20b0902041252l7041062fqc7202db633bb2141@mail.gmail.com>

Op woensdag 04-02-2009 om 15:52 uur [tijdzone -0500], schreef Cheyenne
Solo:

> I've started using Fedora 7 so I can use the strict policy and its
> user mapping capabilities for my (A)RBAC experimentation.

You can use RBAC just as well with Fedora 10. If required you can even
uninstall the unconfined module which will turn your targeted policy
into strict policy. Fedora 7 policy is no longer maintained.

> I have hit a different roadblock, however, dealing with custom user
> mappings: I cannot get users I've created to map to SELinux users I've
> defined. I've declared the users and their roles and types in a module
> that I have installed into the policy. 

Are you sure that this module is proper?

> When I added mappings to /etc/selinux/strict/seusers , either by hand
> or with semanage, the user ends up with the context
> system_u:system_r:xdm_t:SystemHigh-SystemLow. 

Are you sure that the mappings are create properly?

> I have files in the /etc/selinux/strict/contexts/users/ directory for
> each user and have put the types and roles appropriately in the
> default_type file. 

Did you also edit the contexts in the user contexts file? Not sure what
if anything is required in the default_type file.

> How does the login process really determine these mappings, and why
> would all of my custom mappings be redirected to
> system_u:system_r:xdm_t? I am quite puzzled.

Basicly it is the following steps i think.

You create an install a proper user domain.
you add a proper user mapping that has access to your new role.
You add a proper login mapping that maps the Login user to the SELinux
user.
You create a proper default context file. It has the name of the SElinux
user and it has proper default contexts defined in it.

This should, atleast in my view in Fedora 10, do it.

> Thanks,
> Ayla


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

  reply	other threads:[~2009-02-04 21:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-16 17:43 Base module, modules.conf Cheyenne Solo
2009-01-16 19:03 ` Stephen Smalley
2009-01-16 19:23   ` Dominick Grift
2009-01-16 19:52     ` Stephen Smalley
2009-01-19 20:53       ` Jacques Thomas
2009-01-20 14:26         ` Stephen Smalley
2009-01-20 15:58           ` Joe Nall
2009-01-20 19:25             ` Stephen Smalley
2009-01-20 20:31               ` Jacques Thomas
2009-02-04 20:52   ` Cheyenne Solo
2009-02-04 21:53     ` Dominick Grift [this message]
2009-02-05 17:51     ` Stephen Smalley

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=1233784411.6488.28.camel@localhost.localdomain \
    --to=domg472@gmail.com \
    --cc=ayla.cheyenne@gmail.com \
    --cc=dwalsh@redhat.com \
    --cc=sds@tycho.nsa.gov \
    --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.