[roll] Roll fuchsia [security] Add boot args configs to policy This change grabs the boot args keys, represented as config capabilities, from kernel-args-forwarder code and places them into a static config file which Scrutiny can ingest to construct its model of the capability routing graph of the running system. This is useful for auditability, since Scrutiny isn't able to inspect code to determine what capabilities might be presented. Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1446193 Original-Revision: c0440cfc549c1e1b7644cb504cca0c643d121936 GitOrigin-RevId: ae4a26425f26a798f7ccd08a850275a587defd5d Change-Id: I92840d2dcba6ddc4ea6573cbea8a0bf6c7115599
This repository contains Fuchsia's Global Integration manifest files.
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.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.