Skip to content

range_transition revisited

Darrel Goeddel selinux 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest3 patches 19 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/3support for extended range_transitionsinclude/sepol/policydb/context.h include/sepol/policydb/mls_types.h include/sepol/policydb/policydb.h +8 more+0 -04 replies
2/3semantic MLS representation for range_trans_rulescheckpolicy/policy_parse.y libsepol/include/sepol/policydb/expand.h libsepol/include/sepol/policydb/mls_types.h +4 more+0 -09 replies
3/3semantic MLS representation for userscheckpolicy/policy_parse.y libsepol/include/sepol/policydb/policydb.h libsepol/src/expand.c +4 more+0 -08 replies

Reviews trailers per patch

All 3 patches have a Reviewed-by or Acked-by.

PatchJoshua BrindleKarl MacMillanStephen Smalley
1/3A-b A-b A-b
2/3A-b A-b
3/3A-b A-b A-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes. Scroll the table sideways for all 3 reviewers.

Read the v1 thread

Cover letter [PATCH 0/3] range_transition revisited

The kernel portion of the range_transition work has been included in the -mm tree and should go into 2.6.19. I hope that I finally some userspace patches that are acceptable to take advantage of that kernel patch...

The first patch is just an update of the last patch posted to this list:
http://marc.theaimsgroup.com/?l=selinux&m=115471167305358&w=2
This is just an update to the latest svn tree - no logic changes. I separated this out because it seemed that everyone was good with this code.

The second patch addresses the question "Is an mls_range_t semantic enough for use in modules?". Unfortunately, the answer was no.

The third patch used the new semantic MLS representation for storing user's MLS data in modules. This format will allow users in MLS modules in the future.

Note that these patches are intended to go together. There are two new ideas put into the modular policy version, but the number is only bumped once. Once again, I think that the policy formats are ready to go and should support everything we could ever possibly want in the future (well a few things anyway).

As before, this patch only addresses the necessary format changes to get modular support for range_transition statements (and now users). However, it does allow immediate use of the extended range_transition statements where they were valid before.

Signature · 6 lines
Darrel

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to [email protected] with
the words "unsubscribe selinux" without quotes as the message.