[or-cvs] r20842: {projects} Build information that results in a signed apk. This is read (projects/android/trunk/Orbot)

[ioerror@xxxxxxxx]

Author: ioerror
Date: 2009-10-25 01:27:19 -0400 (Sun, 25 Oct 2009)
New Revision: 20842

Modified:
   projects/android/trunk/Orbot/BUILD
Log:
Build information that results in a signed apk.
This is ready to test! Make your own bin/Orbot-signed-alpha.apk and file bugs!


Modified: projects/android/trunk/Orbot/BUILD
===================================================================
--- projects/android/trunk/Orbot/BUILD	2009-10-25 05:11:16 UTC (rev 20841)
+++ projects/android/trunk/Orbot/BUILD	2009-10-25 05:27:19 UTC (rev 20842)
@@ -98,3 +98,29 @@
 	ant release
 
 This will produce an unsigned Tor package in ./bin/Orbot-unsigned.apk!
+
+To produce a usable package, you'll need to sign the .apk. The basics on
+signing can be found on the Android developer site:
+
+	http://developer.android.com/guide/publishing/app-signing.html
+
+The three steps are quite simple. First, you'll generate a key. Secondly,
+you'll sign the application. Thirdly, you'll verify the the apk.
+
+Generating a signing key:
+
+	keytool -genkey -v -keystore my-release-key.keystore \
+		-alias orbots_key -keyalg RSA -validity 10000
+
+Sign the apk:
+
+	jarsigner -verbose -keystore my-release-key.keystore \
+		bin/Orbot-unsigned.apk orbots_key
+
+Verify the signature for the apk:
+
+	jarsigner -verify bin/Orbot-unsigned.apk
+	mv bin/Orbot-unsigned.apk bin/Orbot-signed-alpha.apk
+
+Now you should have a fully signed and production ready alpha release of Orbot!
+Give bin/Orbot-signed-alpha.apk an install and send us bug reports!