[roll] Roll fuchsia [tee] Teach binder-proxy how to enumerate available TAs

This adds an enumeration API to IMicrofuchsia which enumerates
the available TAs within a TEE instance and returns a list of the UUIDs.
To generate this list, binder-proxy iterates over the "ta" directory
exposed by the TA manager.

This change comes with a hermetic unit test that iterates over the
exposed UUIDs in a test environment. There is also a host tool called
`binder_proxy_host_tool` that uses the Binder RPC protocol to interact
with the proxy over either VSOCK or INET socket. It defaults to the CID
(3) and port used by default by `ffx emu --engine crosvm` and can be
directed to use (presumably forwarded) inet address / port instead.

Original-Bug: 369435662
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1130349
Original-Revision: a74c0b3faf730e502867538027ffc3e8b9c8913a
GitOrigin-RevId: d711f238d6e8bc36f513b53b3005807df3082da1
Change-Id: I9666da3ed991fb08a50b73feab70b5c727e6f8a1
1 file changed
tree: 0a96867444e19fefebc72d9c8fe1065c57b77354
  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.