[roll] Roll fuchsia [assembly][security] Disable scrutiny verification on boards using custom signing scripts

Disable scrutiny's checks that require parsing the zbi, if the board
uses a custom_signing_script.

A custom signing script is meant to be used when the zbi image must be
post-processed in some manner before it can be used by the target
device.  In those cases, the resultant file is likely not readable by
scrutiny, and so these checks do not work as written.

Original-Bug: 100989

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/682824
Original-Revision: a79f5ebbcfe3d3212e54ba2f7b91cc9637011ae5
GitOrigin-RevId: 507254a7ef1f4d2c7f4c1a62d03eb41bb8538e51
Change-Id: I663ef5d95faac3c85dbc767536dc8c91f5cc4aed
1 file changed
tree: 2efe53bb347bf8e62a1a788349962c05349da744
  1. infra/
  2. third_party/
  3. cts
  4. firmware
  5. flower
  6. jiri.lock
  7. minimal
  8. prebuilts
  9. README.md
  10. stem
  11. test_durations
  12. 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.