All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: "Christopher J. PeBenito" <cpebenito@tresys.com>
Cc: Joe Nall <joe@nall.com>, Joshua Brindle <method@manicmethod.com>,
	SE Linux <selinux@tycho.nsa.gov>
Subject: Re: per role template confusion
Date: Fri, 10 Oct 2008 17:27:03 -0400	[thread overview]
Message-ID: <48EFC8A7.3040104@redhat.com> (raw)
In-Reply-To: <1223643494.2165.148.camel@gorn>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Christopher J. PeBenito wrote:
> On Thu, 2008-10-09 at 18:17 -0500, Joe Nall wrote:
>> On Oct 9, 2008, at 3:24 PM, Joshua Brindle wrote:
>>
>>> Joe Nall wrote:
>>>> Can someone explain the per role template implementation? I am  
>>>> confused.
>>>>
>>>> During policy compilation, a .mod.role file is created that just  
>>>> references the roles in /usr/share/selinux/devel/include/rolemap  
>>>> regardless of the roles defined via semanage. Should semanage add  
>>>> roles to rolemap? Is there additional magic in semodule?
>>>>
>>>> joe
>>> Roles aren't created by semanage, only user->role mappings. The  
>>> per_role_template creates derived types for each role (eg.,  
>>> staff_mozilla_t, sysadm_mozilla_t). These roles are defined in the  
>>> policy only.
>> Ok. I thought the role statement just did type mapping and did not  
>> realize there was an implicit role declaration.
>>
>> I would still like an explanation of how this works and if/how new  
>> roles are handled with respect to per role templates.
> 
> For each entry in the rolemap file, the infrastructure calls the
> [modulename]_per_role_template() for each module, if it exists.
> 
This does NOT happen in Fedora.  I have patched this out and force
explicit calls to per_role_templates.  Calling them globably forces all
confined users to transition to per_role_templates even when you don't
want them to.

I believe this is a mistake.
> If (u|r)bacsep succeeds, this will be dropped in favor of explicit
> calls.
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkjvyKcACgkQrlYvE4MpobPzdgCffiTnFd8dU3PbVdYCklN0MCWK
QrcAoOdfb/vgix0G2smLpgSkb0InJEiI
=np8I
-----END PGP SIGNATURE-----

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

      parent reply	other threads:[~2008-10-10 21:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-09 18:36 per role template confusion Joe Nall
2008-10-09 20:24 ` Joshua Brindle
2008-10-09 23:17   ` Joe Nall
2008-10-10 12:58     ` Christopher J. PeBenito
2008-10-10 14:03       ` Joe Nall
2008-10-10 14:29         ` Christopher J. PeBenito
2008-10-10 14:43           ` Joe Nall
2008-10-10 21:27       ` Daniel J Walsh [this message]

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=48EFC8A7.3040104@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=cpebenito@tresys.com \
    --cc=joe@nall.com \
    --cc=method@manicmethod.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.