summaryrefslogtreecommitdiffstats
path: root/docs/depthcharge
diff options
context:
space:
mode:
Diffstat (limited to 'docs/depthcharge')
-rw-r--r--docs/depthcharge/index.html10
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/depthcharge/index.html b/docs/depthcharge/index.html
index d30c2e0..210cde5 100644
--- a/docs/depthcharge/index.html
+++ b/docs/depthcharge/index.html
@@ -26,7 +26,7 @@
</p>
<ul>
- <li><a href="#chromebook_security_model">Chromebook security model</a></li>
+ <li><a href="#cros_security_model">CrOS security model</a></li>
<li><a href="#developer_mode_screen">Developer mode screen</a>
<ul>
<li><a href="#holding_developer_mode_screen">Holding the developer mode screen</li>
@@ -49,18 +49,18 @@
<div class="section">
- <h1 id="chromebook_security_model">Chromebook security model</h1>
+ <h1 id="cros_security_model">CrOS security model</h1>
<p>
- Chromebooks implement a strict security model to ensure that these devices do not become compromised,
+ CrOS (Chromium OS/Chrome OS) devices such as Chromebooks implement a strict security model to ensure that these devices do not become compromised,
that is implemented as the verified boot (vboot) reference, most of which is executed within depthcharge.
- A detailed overview of the Chromebook security model is available on the dedicated page.
+ A detailed overview of the CrOS security model is available on the dedicated page.
</p>
<div class="subsection">
<p>
- In spite of the Chromebook security model, depthcharge won't allow booting kernels without verifying their signature and booting from external media or legacy payload unless explicitly allowed: see <a href="#configuring_verified_boot_parameters">configuring verified boot parameters</a>.
+ In spite of the CrOS security model, depthcharge won't allow booting kernels without verifying their signature and booting from external media or legacy payload unless explicitly allowed: see <a href="#configuring_verified_boot_parameters">configuring verified boot parameters</a>.
</p>
</div>