Verify that the VM-generated BCC is valid

Commit 5430ecaaa2deb9d1e0077c2e2e0a72e89540da76 causes the CompOS VM
to write its BCC to file.

Augment our tests to pull that file and run it through the
bcc_validator to make sure the chain is valid (each entry is
well-formed, the signatures all check out, etc). Also add the BCC file
to the test artifacts.

While I'm here, do some minor tidying up.

Bug: 225177477
Test: atest android.compos.test.ComposTestCase#testOdrefreshSpeed
Change-Id: I544d9086fb875eb8987868555bcb99de42ac7f6b
2 files changed
tree: 5968fb7e9c5a3d35205b5db232dfca670d906181
  1. .prebuilt_info/
  2. apex/
  3. apkdmverity/
  4. authfs/
  5. compos/
  6. demo/
  7. docs/
  8. javalib/
  9. launcher/
  10. libs/
  11. microdroid/
  12. microdroid_manager/
  13. pvmfw/
  14. tests/
  15. virtualizationservice/
  16. vm/
  17. vmbase/
  18. zipfuse/
  19. .clang-format
  20. .gitignore
  21. Android.bp
  22. OWNERS
  23. PREUPLOAD.cfg
  24. README.md
  25. TEST_MAPPING
README.md

Virtualization

This repository contains userspace services related to running virtual machines on Android, especially protected virtual machines. See the getting started documentation and Microdroid README for more information.