[roll] Roll fuchsia [sestarnix] Clean up AccessVector type names

Previously there were 2 types called AccessVector:
one representing a permission set, the other a
permission set + additional data drawn from an
allow, auditallow, dontaudit, or neverallow policy
statement, or data drawn from a type_transition
statement.

This change renames the second type to
AccessVectorRule. "Access vector rule" is a common
name in SELinux documentation for the access
control rule defined by one of first 4 kinds
of statement above. An AccessVectorRule maps a
source, target & class to either an AccessVector
(for "allow", etc) or a TypeId (for
"type_transition" statements)

Also adds a ClassPermissionId type similar to
the existing *Id types for other identifiers,
(though with class scope rather than policy scope).

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1196711
Original-Revision: 69b89b5e3ec809e43db0c97cc73a67c68da4f76b
GitOrigin-RevId: 08cef78fc4683155b3140fb3cf0558fa3a415ef8
Change-Id: Ide5ec6292b9a37ae109b5d1bb35ad3b94d305736
1 file changed
tree: ae83d15e61f6a278c666b9f141bc778c346dd145
  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 in one of the communication channels documented at get involved.

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.