From 1a8bb04a8c4b1678a183f092afa4960ea55b148b Mon Sep 17 00:00:00 2001 From: Daniel Micay Date: Wed, 11 Nov 2020 18:37:58 -0500 Subject: [PATCH] move generating Vanadium signing key earlier --- static/build.html | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/static/build.html b/static/build.html index 96ff2d38..a325a2b2 100644 --- a/static/build.html +++ b/static/build.html @@ -749,6 +749,14 @@ cd ../.. cd Vanadium git checkout $CORRECT_BRANCH_OR_TAG +

Generate a signing key for Vanadium if this is the initial build:

+ +
keytool -genkey -v -keystore vanadium.keystore -storetype pkcs12 -alias vanadium -keyalg RSA -keysize 4096 -sigalg SHA512withRSA -validity 10000 -dname "cn=GrapheneOS"
+ +

You will be prompted to enter a password which will be requested by the + generate_release.sh script for signing releases. You should back up + the generated keystore with your other keys.

+

Fetch the Chromium sources:

fetch --nohooks android
@@ -758,14 +766,6 @@ git checkout $CORRECT_BRANCH_OR_TAG
gclient sync -D --with_branch_heads --with_tags -r $VERSION --jobs 32
-

Generate a signing key for Vanadium if this is the initial build:

- -
keytool -genkey -v -keystore vanadium.keystore -storetype pkcs12 -alias vanadium -keyalg RSA -keysize 4096 -sigalg SHA512withRSA -validity 10000 -dname "cn=GrapheneOS"
- -

You will be prompted to enter a password which will be requested by the - generate_release.sh script for signing releases. You should back up - the generated keystore with your other keys.

-

Apply the GrapheneOS patches on top of the tagged release:

cd src