Re: [PATCH v4] Add default_range glblub support

From: Paul Moore <paul@paul-moore.com>
To: Stephen Smalley <sds@tycho.nsa.gov>,
	jwcart2 <jwcart2@tycho.nsa.gov>,
	Joshua Brindle <joshua.brindle@crunchydata.com>
Cc: selinux@vger.kernel.org
Subject: Re: [PATCH v4] Add default_range glblub support
Date: Mon, 7 Oct 2019 19:08:27 -0400	[thread overview]
Message-ID: <CAHC9VhTR1=x_c9hYURFCy+DhsKZHT9RhCGM-K=UrhZBHmO39kA@mail.gmail.com> (raw)
In-Reply-To: <16d98abe468.280e.85c95baa4474aabc7814e68940a78392@paul-moore.com>

On Fri, Oct 4, 2019 at 5:27 PM Paul Moore <paul@paul-moore.com> wrote:
>
> It's in the queue. Two things have delayed things a bit this week: I'm traveling which has limited my time, and the - rc1 Rawhide kernels have been crashing at boot (it doesn't appear to be SELinux related) which has complicated testing.
>
> In general you can always check the SELinux patchwork, if the state is marked as "New" then it is in the queue.
>
> https://patchwork.kernel.org/project/selinux/list

... and now it's merged, although I did have to fix some line length
issues (hint to Josh: run scripts/checkpatch.pl next time).  Thanks
everyone.

> On October 4, 2019 2:10:31 PM Stephen Smalley <sds@tycho.nsa.gov> wrote:
>
> > On 9/11/19 7:52 PM, Paul Moore wrote:
> >> On Tue, Sep 10, 2019 at 1:27 PM jwcart2 <jwcart2@tycho.nsa.gov> wrote:
> >>> On 9/9/19 2:05 PM, Joshua Brindle wrote:
> >>>> Policy developers can set a default_range default to glblub and
> >>>> computed contexts will be the intersection of the ranges of the
> >>>> source and target contexts. This can be used by MLS userspace
> >>>> object managers to find the range of clearances that two contexts
> >>>> have in common. An example usage is computing a transition between
> >>>> the network context and the context of a user logging into an MLS
> >>>> application.
> >>>>
> >>>> For example, one can add a default with
> >>>> this cil:
> >>>>
> >>>> (defaultrange db_table glblub)
> >>>>
> >>>> or in te (base module only):
> >>>>
> >>>> default_range db_table glblub;
> >>>>
> >>>> and then test using the compute_create utility:
> >>>>
> >>>> $ ./compute_create system_u:system_r:kernel_t:s0:c1,c2,c5-s0:c1.c20 system_u:system_r:kernel_t:s0:c0.c20-s0:c0.c36 db_table
> >>>> system_u:object_r:kernel_t:s0:c1,c2,c5-s0:c1.c20
> >>>>
> >>>> Some example range transitions are:
> >>>>
> >>>> User Permitted Range | Network Device Label | Computed Label
> >>>> ---------------------|----------------------|----------------
> >>>> s0-s1:c0.c12         | s0                   | s0
> >>>> s0-s1:c0.c12         | s0-s1:c0.c1023       | s0-s1:c0.c12
> >>>> s0-s4:c0.c512        | s1-s1:c0.c1023       | s1-s1:c0.c512
> >>>> s0-s15:c0,c2         | s4-s6:c0.c128        | s4-s6:c0,c2
> >>>> s0-s4                | s2-s6                | s2-s4
> >>>> s0-s4                | s5-s8                | INVALID
> >>>> s5-s8                | s0-s4                | INVALID
> >>>>
> >>>> Signed-off-by: Joshua Brindle <joshua.brindle@crunchydata.com>
> >>>
> >>> Merged.
> >>> Thanks,
> >>> Jim
> >>
> >> Thanks guys.  We're at -rc8 for the kernel right now so it's a little
> >> late to pull the corresponding kernel patch, but I'll do that after
> >> the merge window closes.
> >
> > Where does this patch stand?
>
>
>

-- 
paul moore
www.paul-moore.com