Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

AVB and trust boundaries

VERIFIED OFFLINE (descriptor integrity) · UNVERIFIED (bootloader acceptance). Research: DOCS/restructuring/c28/C28-AVB-TRUST-MODEL.md, C28-BOOTLOADER-ACCEPTANCE-GATES.md, LIEPPOS-C28-AVB-TRUST.md @ ae6dce06.

Six mechanisms that are easy to conflate

#MechanismStatus
1AVB root trustFactory root is signed with the public AOSP testkey_rsa2048 (cdbb7717…). The C28 root uses the same key, so the root-trust relationship is identical to stock
2OEM boot chainKey 9d808b09… signs the stock boot footer. Not reproduced. C28 binds boot with a root hash descriptor over the C26 image instead of the location-3 chain
3Boot-image signature metadataStock boot.img is header v4 with signature_size = 0, so it has no v4 signature block. The earlier claim that the footer is a confirmed Google GKI key is superseded: it cannot be confirmed from the images
4Kernel module signing60 GKI modules signed with the C26 kernel’s own module key, whose certificate is embedded in the C26 Image (see DLKM)
5dm-verityHashtrees present for system, system_ext, product, odm_dlkm, system_dlkm, vendor_dlkm; bring-up on hardware unverified
6Bootloader acceptanceUNVERIFIED. No gate was exercised

A successful AVB verification with a development key is not proof of bootloader acceptance. AVB and the GKI boot-signature mechanism are independent; neither replaces the other.

Observed, not guaranteed

  • Stock boots with a root signed by the AOSP test key; the live Slot-A root has flags = 3 and an invalid signature, yet boots — the bootloader appears unlocked or permissive.
  • Slot-B root a9d8cd21… (experiment key d6b1afef…) reached Android 17 second-stage init on 2026-10-03, so LK accepted a non-stock root key.

Hardware gates (all open)

#GatePass criterion
G1Lock statero.boot.verifiedbootstate, ro.boot.vbmeta.device_state
G2Root with flags = 0LK reaches kernel; /proc/pl_lk, pstore
G3boot as root hash descriptorLK does not require the OEM chain
G4GKI boot signaturenot required (signature_size = 0)
G5Rollbackstored indexes 0/2/4 ≤ 0; location 3 unreferenced
G6Module signingno -EACCES for the 60 GKI modules
G7dm-veritysystem_dlkm / vendor_dlkm verity devices appear
G8First-stage UFSufs-mediatek-mod probes, super appears

None exercised. Hardware validation: 0.

Rollback

Every C28 rollback index is 0, matching the factory values for locations 0, 2 and 4. Location 3 (boot chain) is no longer referenced. Device-stored rollback values were not captured offline.

Hazard: do not flash a Slot-B package to a production device. The bound stock Android 15 userspace needs 4,948.9 MiB; Slot B offers 2,173.7 MiB. The verdict is OFFLINE_PREFLIGHT_FAILED.