[roll] Roll fuchsia [fshost] mock boot instead of falling back to pkg The zxcrypt configuration exists in /boot/config at runtime. For the integration tests, we included a config/zxcrypt in the test fshost package, so the path was /pkg/config/zxcrypt. To work around this, get_policy had a fallback mechanism. There is no reason to do it like this anymore. We can mock /boot in the tests to provide whatever the test would like. Now we provide a read only file for the zxcrypt policy, and remove the fallback. The only thing that used get_policy to read the policy file was fshost. This also removes the x permission from boot. I'm pretty sure we don't execute anything from boot anymore now that we are a bootfs package - all the binaries we need are either included in our package or resolved as packages via the boot resolver. This is verified by CQ and by the fact that we were never giving any form of /boot to fshost in the integration tests so it's apparently not that important - I think it's only used for the zxcrypt policy right now. Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1260468 Original-Revision: 3f4d1ed98bb98794741449f7137e61b707542c01 GitOrigin-RevId: 480da78f4023627fae9bd81c020cbaa44a4d4c49 Change-Id: I7723982a803806afa3ea57450781c2d1d92523d6
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.