move generating Vanadium signing key earlier

This commit is contained in:
Daniel Micay 2020-11-11 18:37:58 -05:00
parent b257eb0a05
commit 1a8bb04a8c

View File

@ -749,6 +749,14 @@ cd ../..</pre>
cd Vanadium
git checkout $CORRECT_BRANCH_OR_TAG</pre>
<p>Generate a signing key for Vanadium if this is the initial build:</p>
<pre>keytool -genkey -v -keystore vanadium.keystore -storetype pkcs12 -alias vanadium -keyalg RSA -keysize 4096 -sigalg SHA512withRSA -validity 10000 -dname "cn=GrapheneOS"</pre>
<p>You will be prompted to enter a password which will be requested by the
<code>generate_release.sh</code> script for signing releases. You should back up
the generated keystore with your other keys.</p>
<p>Fetch the Chromium sources:</p>
<pre>fetch --nohooks android</pre>
@ -758,14 +766,6 @@ git checkout $CORRECT_BRANCH_OR_TAG</pre>
<pre>gclient sync -D --with_branch_heads --with_tags -r $VERSION --jobs 32</pre>
<p>Generate a signing key for Vanadium if this is the initial build:</p>
<pre>keytool -genkey -v -keystore vanadium.keystore -storetype pkcs12 -alias vanadium -keyalg RSA -keysize 4096 -sigalg SHA512withRSA -validity 10000 -dname "cn=GrapheneOS"</pre>
<p>You will be prompted to enter a password which will be requested by the
<code>generate_release.sh</code> script for signing releases. You should back up
the generated keystore with your other keys.</p>
<p>Apply the GrapheneOS patches on top of the tagged release:</p>
<pre>cd src