summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Micay <daniel.micay@grapheneos.org>2025-02-14 11:49:47 -0500
committerDaniel Micay <daniel.micay@grapheneos.org>2025-02-14 11:53:40 -0500
commita6e3d4bf85492e79fac4da8454cce093a5faaab5 (patch)
tree576f4c97f2a9595e454c4340c0cfb5b0d5205a1b
parent7a684a35091c1005675cc48f8493371e663a0ef6 (diff)
drop key rotation verification instructions
We moved from signify to OpenSSH on 2024-02-14. These instructions were useful but are consistently causing confusion for people who are missing that this is an optional step for people who had the signify public key saved from previous usage. We provide multiple ways to get the current public key and don't really need this.
-rw-r--r--static/install/cli.html7
1 files changed, 0 insertions, 7 deletions
diff --git a/static/install/cli.html b/static/install/cli.html
index d746d8e6..341f1a82 100644
--- a/static/install/cli.html
+++ b/static/install/cli.html
@@ -428,13 +428,6 @@ Installed as /home/username/platform-tools/fastboot</pre>
<li><a href="https://github.com/GrapheneOS/releases.grapheneos.org/blob/main/static/allowed_signers">GitHub</a></li>
</ul>
- <p>The current public key is signed with the previous signify key. If you already
- have the previous signify public key (factory.pub) and want to verify the new key
- with it:</p>
-
- <pre>curl -O https://releases.grapheneos.org/allowed_signers.sig
-signify -V -m allowed_signers -x allowed_signers.sig -p factory.pub</pre>
-
<p>When the current signing key is replaced, the new key will be signed with it.</p>
<p>Download the factory images for the device from <a href="/releases">the releases