From ff3437b9e827e71d216c3228e837688b3c361bef Mon Sep 17 00:00:00 2001 From: Daniel Micay Date: Sat, 14 Mar 2020 17:25:59 -0400 Subject: [PATCH] change key alias to vanadium --- static/build.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/static/build.html b/static/build.html index 03eb93f5..74ec5750 100644 --- a/static/build.html +++ b/static/build.html @@ -593,7 +593,7 @@ git am --whitespace=nowarn ../*.patch

Generate a signing key for Vanadium if this is the initial build (the sample password configured in args.gn is vanadiumpass):

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

You should back this up with your other keys.

@@ -609,7 +609,7 @@ git am --whitespace=nowarn ../*.patch

You need to set trichrome_certdigest to the correct value for your generated signing key. You can obtain this with the following command:

-
keytool -export-cert -alias vanadiumkey -keystore vanadium.keystore | sha256sum
+
keytool -export-cert -alias vanadium -keystore vanadium.keystore | sha256sum

Build the components: