自 2025 年 3 月 27 日起,我們建議您使用 android-latest-release
而非 aosp-main
建構及貢獻 AOSP。詳情請參閱「Android 開放原始碼計畫變更」。
通過驗證的開機程序
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
驗證開機程序會盡力確保所有執行程式碼都來自可信任的來源 (通常是裝置原始設備製造商),而非來自攻擊者或已損毀。它會建立完整的信任鏈結,從硬體保護的信任根開始,再到系統啟動載入程式、啟動分區和其他已驗證的分區,包括 system
、vendor
和選用的 oem
分區。在裝置啟動期間,每個階段會在移交執行作業前,驗證下一個階段的完整性和真實性。
除了確保裝置執行安全的 Android 版本,驗證開機程序還會透過回溯保護機制檢查正確的 Android 版本。復原保護機制可確保裝置只更新至較新的 Android 版本,進而避免潛在的漏洞持續存在。
除了驗證作業系統外,Verified Boot 還可讓 Android 裝置向使用者傳達完整性狀態。
背景
Android 4.4 新增了對 Verified Boot 和 dm-verity 核心功能的支援。這項驗證功能組合可做為驗證開機程序 1 的功能。
先前版本的 Android 會警告使用者裝置毀損,但仍允許他們啟動裝置,而 Android 7.0 開始嚴格執行「驗證啟動」機制,以防受損裝置啟動。Android 7.0 也新增了對前向錯誤修正功能的支援,可提高在非惡意資料毀損情況下的可靠性。
Android 8.0 以上版本包含 Android 驗證開機程序 (AVB),這是與 Treble 計畫相容的驗證開機程序參考實作項目。除了與 Treble 搭配使用之外,AVB 也將分割區尾端格式標準化,並新增了回溯保護功能。
這個頁面中的內容和程式碼範例均受《內容授權》中的授權所規範。Java 與 OpenJDK 是 Oracle 和/或其關係企業的商標或註冊商標。
上次更新時間:2025-07-27 (世界標準時間)。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["缺少我需要的資訊","missingTheInformationINeed","thumb-down"],["過於複雜/步驟過多","tooComplicatedTooManySteps","thumb-down"],["過時","outOfDate","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["示例/程式碼問題","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-07-27 (世界標準時間)。"],[],[],null,["# Verified Boot strives to ensure all executed code comes from a trusted source\n(usually device OEMs), rather than from an attacker or corruption. It\nestablishes a full chain of trust, starting from a hardware-protected root of\ntrust to the bootloader, to the boot partition and other verified partitions\nincluding `system`, `vendor`, and optionally\n`oem` partitions. During device boot up, each stage verifies the\nintegrity and authenticity of the next stage before handing over execution.\n\n\nIn addition to ensuring that devices are running a safe version of Android,\nVerified Boot checks for the correct version of Android with\n[rollback\nprotection](/docs/security/features/verifiedboot/verified-boot#rollback-protection). Rollback protection helps to prevent a possible\nexploit from becoming persistent by ensuring devices only update to newer\nversions of Android.\n\n\nIn addition to verifying the OS, Verified Boot also allows Android devices to\ncommunicate their state of integrity to the user.\n\nBackground\n----------\n\n\nAndroid 4.4 added support for Verified Boot and the\n[dm-verity](/docs/security/features/verifiedboot/dm-verity) kernel feature. This\ncombination of verifying features served as Verified Boot 1.\n\n\nWhere previous versions of Android warned users about device corruption, but\nstill allowed them to boot their devices, Android 7.0 started strictly enforcing\nVerified Boot to prevent compromised devices from booting. Android 7.0 also\nadded support for forward error correction to improve reliability against\nnon-malicious data corruption.\n\n\nAndroid 8.0 and higher includes\n[Android Verified Boot](/docs/security/features/verifiedboot/avb) (AVB), a\nreference implementation of Verified Boot that works with Project Treble. In\naddition to working with Treble, AVB standardized partition footer format and\nadded rollback protection features."]]