[roll] Roll fuchsia [tee] Check max key size in operation allocation

We introduce a simple pattern for max key size checking, layering things
atop the existing carve-out for api_impl::storage key size logic.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1199407
Original-Revision: cb1100056c48c28cd7f697f2e08f1f75c0162b37
GitOrigin-RevId: 0d92750d45765a8b3ea9c4698c8af039e602bc25
Change-Id: Ide2cba1f5dbaf82233062c3e2d2d88cec238b8a4
1 file changed
tree: c874be09220fcbd25baf956df1b954e65c6042d9
  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.