From: Dominick Grift <dac.override@gmail.com>
To: selinux@tycho.nsa.gov
Subject: Re: [PATCH v2 0/1] supporting RBACSEP in genhomedircon
Date: Thu, 6 Oct 2016 14:17:22 +0200 [thread overview]
Message-ID: <e9fe21ba-ebf5-ebb2-911e-da8a02be0ca2@gmail.com> (raw)
In-Reply-To: <cover.1475590141.git.gary.tierney@gmx.com>
[-- Attachment #1.1: Type: text/plain, Size: 2355 bytes --]
On 10/06/2016 01:09 PM, Gary Tierney wrote:
> New version of the previous genhomedircon-rbacsep patch with some changes. A
> bit of a delay as I had to get in a libsepol/cil fix which was blocking this.
>
> 1. Remove semanage.conf option
> 2. Drop unrelated change
> 3. Adds a new homedir_role member to the genhomedircon_user struct.
> 4. Sets homedir_role if the SELinux users prefix is a valid role for that user.
> 5. Replaces all roles with homedir_role in context specifications if homedir_role is set.
>
> One issue that came up when writing these patches is that genhomedircon
> squashes logging [1] for some reason, which can result in no warning / info
> messages and an empty file_contexts.homedirs file if policy has been
> incorrectly configured. Can we get rid of this behavior or add a flag to
> conditionally enable logging?
>
If we do that then i suspect that we can also use that for the messages
where an seuser id cannot be found (e.g. that system_u, and gdm.id issue)
> Dominick Grift helpfully created some test images that demo DSSP policy working
> with both RBACSEP and non-RBACEP:
> https://tfirg.asu.su/2016/10/03/garys-patches/
>
> There are still some rough edges though, for example in policy you can't write a
> statement like: (userprefix id role) and put it in an abstract namespace,
> since it is interpreted as a literal:
>
> (block usersubj
> (blockabstract usersubj)
> (user id)
> (role role)
> (userrole id role)
> (userprefix id role))
>
> (block wheel
> (blockinherit usersubj))
>
> Which leaves us with a (userid, prefix) tuple of (wheel.id, role) [wheel.id
> might even just be id here, haven't checked if users are expanded or also taken
> as literals].
>
> Though this is something I can look at later if all is well here.
>
> [1] https://github.com/SELinuxProject/selinux/blob/master/libsemanage/src/genhomedircon.c#L568-L572
>
> Gary Tierney (1):
> genhomedircon: use userprefix as the role for homedir content
>
> libsemanage/src/genhomedircon.c | 38 +++++++++++++++++++++++++++++++++++---
> 1 file changed, 35 insertions(+), 3 deletions(-)
>
--
Key fingerprint = 5F4D 3CDB D3F8 3652 FBD8 02D5 3B6C 5F1D 2C7B 6B02
https://sks-keyservers.net/pks/lookup?op=get&search=0x3B6C5F1D2C7B6B02
Dominick Grift
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 648 bytes --]
next prev parent reply other threads:[~2016-10-06 12:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 11:09 [PATCH v2 0/1] supporting RBACSEP in genhomedircon Gary Tierney
2016-10-06 11:09 ` [PATCH v2 1/1] genhomedircon: use userprefix as the role for homedir content Gary Tierney
2016-10-06 13:53 ` Stephen Smalley
2016-10-06 12:17 ` Dominick Grift [this message]
2016-10-06 13:29 ` [PATCH v2 0/1] supporting RBACSEP in genhomedircon Stephen Smalley
2016-10-06 14:56 ` James Carter
2016-10-06 15:29 ` Dominick Grift
2016-10-06 16:49 ` James Carter
2016-10-06 17:23 ` [SUSPECTED SPAM] [SUSPICIOUS MESSAGE] " Dominick Grift
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=e9fe21ba-ebf5-ebb2-911e-da8a02be0ca2@gmail.com \
--to=dac.override@gmail.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.