dexter submitted this change.

View Change

README.md: add section that explains re-signing of the APK file.

Some users may already have an existing keystore + ARA-M configuration
on their cards. Let's explain how the APK file can be re-signed with
those keys.

Related: OS#6367
Change-Id: I7ccf7ed2c7e8dfd1217afd46c983d4f79ebef124
---
M README.md
1 file changed, 17 insertions(+), 0 deletions(-)

diff --git a/README.md b/README.md
index 801e4f3..c5d1ebb 100644
--- a/README.md
+++ b/README.md
@@ -246,3 +246,20 @@
 
 Pre-built (nightly) APK packages are avilable for download under:
 * https://jenkins.osmocom.org/jenkins/job/master-android-apdu-proxy/a1=default,a2=default,a3=default,a4=default,label=osmocom-master/
+
+Re-signing APK
+--------------
+
+In case the user already has an ARA-M configuration with matching signing keys,
+it is possible to use the `apksigner` utility to re-sign an already existing APK
+file with those keys.
+
+The following commandline will re-sign `app-release.apk` with `myKey` from the
+user specified keystore `/path/to/my/keystore.jks`.
+
+```
+$ apksigner sign --ks-key-alias myKey --ks-pass "pass:myPassword" --ks /path/to/my/keystore.jks ./app/build/outputs/apk/release/app-release.apk
+```
+
+To make sure that the re-signing was successful the apksigner utility can be
+used as already described in section `Signing and ARA-M configuration`
\ No newline at end of file

To view, visit change 38838. To unsubscribe, or for help writing mail filters, visit settings.