aboutsummaryrefslogtreecommitdiff
path: root/docs/depthcharge
diff options
context:
space:
mode:
authorAlyssa Rosenzweig <alyssa@rosenzweig.io>2017-03-17 23:29:23 -0700
committerAlyssa Rosenzweig <alyssa@rosenzweig.io>2017-03-17 23:29:23 -0700
commit62f6c9d95fa1546bf5b3d65d8aa7da92e14c82ab (patch)
treec1e770329be2715a674c8bbfc026a17050bcf86a /docs/depthcharge
parent1eb5130a1c70a7238548d977e9c6f371c007eed7 (diff)
downloadlibrebootfr-62f6c9d95fa1546bf5b3d65d8aa7da92e14c82ab.tar.gz
librebootfr-62f6c9d95fa1546bf5b3d65d8aa7da92e14c82ab.zip
Squeeze blank
Diffstat (limited to 'docs/depthcharge')
-rw-r--r--docs/depthcharge/index.md30
1 files changed, 0 insertions, 30 deletions
diff --git a/docs/depthcharge/index.md b/docs/depthcharge/index.md
index 55445e61..e5d75550 100644
--- a/docs/depthcharge/index.md
+++ b/docs/depthcharge/index.md
@@ -4,7 +4,6 @@ Depthcharge payload
This section relates to the depthcharge payload used in libreboot.
-
- [CrOS security model](#cros_security_model)
- [Developer mode screen](#developer_mode_screen)
- Holding the developer mode screen
@@ -18,8 +17,6 @@ This section relates to the depthcharge payload used in libreboot.
- [Configuring verified boot
parameters](#configuring_verified_boot_parameters)
-
-
CrOS security model {#cros_security_model}
===================
@@ -29,15 +26,11 @@ compromised, that is implemented as the verified boot (vboot) reference,
most of which is executed within depthcharge. A detailed overview of the
CrOS security model is available on the dedicated page.
-
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 [configuring
verified boot parameters](#configuring_verified_boot_parameters).
-
-
-
Developer mode screen {#developer_mode_screen}
=====================
@@ -52,7 +45,6 @@ external media (when enabled), booting from legacy payload (when
enabled), showing information about the device and disabling developer
mode.
-
Holding the developer mode screen {#holding_developer_mode_screen}
---------------------------------
@@ -60,8 +52,6 @@ As instructed on the developer mode screen, the screen can be held by
pressing **Ctrl + H** in the first 3 seconds after the screen is shown.
After that delay, depthcharge will resume booting normally.
-
-
Booting normally {#booting_normally}
----------------
@@ -71,8 +61,6 @@ after **3 seconds** (if developer mode screen is not held).
The default boot medium (internal storage, external media, legacy
payload) is shown on screen.
-
-
Booting from different mediums {#booting_different_mediums}
------------------------------
@@ -88,8 +76,6 @@ can be triggered by pressing various key combinations:
- External media: **Ctrl + U** (when enabled)
- Legacy payload: **Ctrl + L** (when enabled)
-
-
Showing device information {#showing_device_information}
--------------------------
@@ -99,9 +85,6 @@ can be triggered by pressing **Ctrl + I** or **Tab**.
Various information is shown, including vboot non-volatile data, TPM
status, GBB flags and key hashes.
-
-
-
Warnings
--------
@@ -111,9 +94,6 @@ The developer mode screen will show warnings when:
- Booting from external media is enabled
- Booting legacy payloads is enabled
-
-
-
Recovery mode screen {#recovery_mode_screen}
====================
@@ -124,7 +104,6 @@ It allows recovering the device from a bad state by booting from a
trusted recovery media. When accessed with the device in a good state,
it also allows enabling developer mode.
-
Recovering from a bad state {#recovering_bad_state}
---------------------------
@@ -154,8 +133,6 @@ replaced. When the recovery private key is available (e.g. when using
self-generated keys), it can be used to sign a kernel for recovery
purposes.
-
-
Enabling developer mode {#enabling_developer_mode}
-----------------------
@@ -165,9 +142,6 @@ by pressing **Ctrl + D**.
Instructions to confirm enabling developer mode are then shown on
screen.
-
-
-
Configuring verified boot parameters {#configuring_verified_boot_parameters}
====================================
@@ -194,7 +168,6 @@ of the device**. In particular, disabling kernels signature
verification, external media boot and legacy payload boot can weaken the
security of the device.
-
The following parameters can be configured:
- Kernels signature verification:
@@ -229,9 +202,6 @@ The following parameters can be configured:
# **crossystem dev\_default\_boot=legacy**
-
-
-
Copyright © 2015 Paul Kocialkowski <contact@paulk.fr>
Permission is granted to copy, distribute and/or modify this document