Build information that results in a signed apk.
This is ready to test! Make your own bin/Orbot-signed-alpha.apk and file bugs! svn:r20842
This commit is contained in:
parent
32ec6efd77
commit
31630b31f9
26
BUILD
26
BUILD
|
@ -98,3 +98,29 @@ Finally, we'll make a proper Android package with ant and the Android App SDK:
|
||||||
ant release
|
ant release
|
||||||
|
|
||||||
This will produce an unsigned Tor package in ./bin/Orbot-unsigned.apk!
|
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!
|
||||||
|
|
Loading…
Reference in New Issue