summaryrefslogtreecommitdiff
path: root/static
diff options
context:
space:
mode:
authorDaniel Micay <danielmicay@gmail.com>2019-08-05 15:50:43 -0400
committerDaniel Micay <danielmicay@gmail.com>2019-08-05 15:50:43 -0400
commit9b427497385f5995fba2b93f6ecaf0a8ba911a8e (patch)
treee855e2eef1f9d65962b8427f831feba0b8b04953 /static
parent5474dd493fef782102eacb73f02d4cb0bf965c07 (diff)
releases: add spacing for ease of reading the html
Diffstat (limited to 'static')
-rw-r--r--static/releases.html4
1 files changed, 4 insertions, 0 deletions
diff --git a/static/releases.html b/static/releases.html
index 2a545185..e8b1ce1e 100644
--- a/static/releases.html
+++ b/static/releases.html
@@ -97,8 +97,10 @@
<p>These releases are available as both tags in the source code repositories and
official builds.</p>
+
<p>The factory images are used for the initial installation and can be verified with
signify. See the <a href="/install">installation guide</a> for details.</p>
+
<p>GrapheneOS uses automatic over-the-air updates, but full update packages are listed
below for uncommon use cases like never connecting the device to the internet. A full
update package can upgrade from any past version to the new version. The over-the-air
@@ -106,12 +108,14 @@
but may be in the future once they're being used more consistently. Update packages
are not for performing the initial installation and you should ignore incorrect guides
trying to use them to install the OS.</p>
+
<p>The update packages have a internal signature verified by the update client (or
recovery image when sideloading). Downgrade attacks are also prevented, and downgrades
cannot be done unless a special downgrade update package has been signed with the
release key. The internal payload for <code>update_engine</code> is also signed,
providing another layer of signature verification and downgrade protection. Verified
boot and the hardware-backed keystore also act as a final layer of protection.</p>
+
<p>Releases are tested by the developers and are then pushed out via the Beta channel.
The release is then pushed out via the Stable channel after being tested by some users
using the Beta channel. In some cases, problems are caught during Beta channel testing