[roll] Roll fuchsia [starnix][selinux] Use policy-defined Ids in SecurityContext fields

Replace strings in SecurityContext field values with policy-defined
(numeric) identifiers.  This removes the need to map from strings
to Ids when looking up rules, and ensures that if a SID can be
resolved to a Context then the fields are guaranteed to have values
actually defined by the policy.

Consistency of fields e.g. range levels, whether the role is
valid for the user, will be landed separately.

Original-Bug: 328375715, 319232900, 330677360
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1011912
Original-Revision: 05d36a2693d06cac5e7687bcbafa56b642c14119
GitOrigin-RevId: d64c415e6e89e32ff04a9670a3e093fddcb2b542
Change-Id: I66fd0273e15c8f6290fa9147bbef9036fb38b5a5
1 file changed
tree: b288595a7e516e0a74a83e808623e966768af934
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.