Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
You can just use these instructions from the official announcement at Open Whisper Systems's blog:
# Clone the Signal Android source repository $ git clone https://github.com/WhisperSystems/Signal-Android.git && cd Signal-Android # Check out the release tag for the version you'd like to compare $ git checkout v[the version number] # Build using the Docker environment $ docker run --rm -v $(pwd):/project -w /project whispersystems/signal-android:1.2 ./gradlew clean assembleRelease # Verify the APKs $ apkdiff/apkdiff.py build/outputs/apks/project-release-unsigned.apk path/to/SignalFromPlay.apk
Note that the instructions above use a pre-built Signal Docker image from Docker Hub. If you wish to compile the image yourself, continue reading the longer version below.
Since version 3.15.0 Signal for Android has supported reproducible builds. This is achieved by replicating the build environment as a Docker image. You'll need to build the image, run a container instance of it, compile Signal inside the container and finally compare the resulted APK to the APK that is distributed in the Google Play Store.
The command line parts in this guide are written for Linux but with some little modifications you can adapt them to macOS (OS X) and Windows. In the following sections we will use
3.15.2 as an example Signal version. You'll just need to replace all occurrences of
3.15.2 with the version number you are about to verify.
Setting up directories
First let's create a new directory for this whole reproducible builds project. In your home folder (
~), create a new directory called
user@host:$ mkdir ~/reproducible-signal
Next create another directory inside
user@host:$ mkdir ~/reproducible-signal/apk-from-google-play-store
We will use this directory to share APKs between the host OS and the Docker container.
Finally create one more directory inside
user@host:$ mkdir ~/reproducible-signal/image-build-context
This directory will be used later to build our Docker image.
Getting the Google Play Store version of Signal APK
To compare the APKs we of course need a version of Signal from the Google Play Store.
First make sure that the Signal version you want to verify is installed on your Android device. You'll need
adb for this part.
Plug your device to your computer and run:
user@host:$ adb shell pm path org.thoughtcrime.securesms
This will output something like:
The output will tell you where the Signal APK is located in your device. (In this example the path is
Now using this information, pull the APK from your device to the
reproducible-signal/apk-from-google-play-store directory you created before:
user@host:$ adb pull \ /data/app/org.thoughtcrime.securesms-1/base.apk \ ~/reproducible-signal/apk-from-google-play-store/Signal-3.15.2.apk
We will use this APK in the final part when we compare it with the self-built APK from GitHub.
Install Docker by following the instructions for your platform at https://docs.docker.com/engine/installation/
Your platform might also have its own preferred way of installing Docker. E.g. Ubuntu has its own Docker package (
docker.io) if you do not want to follow Docker's instructions.
In the following sections we will assume that your Docker installation works without issues. So after installing, please make sure that everything is running smoothly before continuing.
Building a Docker image for Signal
First you will need the
Dockerfile for Signal Android. It comes bundled with Signal's source code. The
Dockerfile contains instructions on how to automatically build a Docker image for Signal. You just need to run it and it builds itself.
Dockerfile to the
user@host:$ wget -O ~/reproducible-signal/image-build-context/Dockerfile_v3.15.2 \ https://raw.githubusercontent.com/WhisperSystems/Signal-Android/v3.15.2/Dockerfile
Note that the
Dockerfile is specific to the Signal version you want to compare to. Again you have to adjust the URL above to match the right version. (Though sometimes the file might not be up to date, see the Troubleshooting section)
Building the image
Now we have everything we need to build the Docker image for Signal. Go to the
user@host:$ cd ~/reproducible-signal/image-build-context
And list the contents.
The output should look like this:
Now in this directory build the image using
user@host:$ docker build --file Dockerfile_v3.15.2 --tag signal-android .
(Note that there is a dot at the end of that command!)
Wait a few years for the build to finish...
(Depending on your computer and network connection, this may take several minutes.)
After the build has finished, you may wish to list all your Docker images to see that it's really there:
user@host:$ docker images
Output should look something like this:
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE signal-android latest c6b84450b896 46 seconds ago 2.94 GB ubuntu 14.04.3 8693db7e8a00 9 weeks ago 187.9 MB
Compiling Signal inside a container
Next we will run a container of the image we just built, grab Signal's source code and compile Signal.
First go to the
user@host:$ cd ~/reproducible-signal/
To run a new ephemeral container with an interactive terminal session execute the following long command:
user@host:$ docker run \ --name signal \ --rm \ --interactive \ --tty \ --volume $(pwd)/apk-from-google-play-store:/signal-build/apk-from-google-play-store \ --workdir /signal-build \ signal-android
Now you are inside the container.
Grab Signal's source code from GitHub and go to the repository directory:
root@container:# git clone https://github.com/WhisperSystems/Signal-Android.git root@container:# cd Signal-Android
Before you can compile, you must ensure that you are at the right commit. In other words you must checkout the version you wish to verify (here we are verifying 3.15.2):
root@container:# git checkout --quiet v3.15.2
Now you may compile the release APK by running:
root@container:# ./gradlew clean assembleRelease
This will take a few minutes
Checking if the APKs match
After the build has completed successfully we can finally compare if the APKs match. For the comparison we need of course the Google Play Store version of Signal APK which you copied to the
apk-from-google-play-store directory in the beginning of this guide. Because we used that directory as a
--volume parameter for our container, we can see all the files in that directory within our container.
So now we can just compare the APKs using the
root@container:# apkdiff/apkdiff.py \ build/outputs/apk/Signal-Android-release-unsigned.apk \ ../apk-from-google-play-store/Signal-3.15.2.apk
If you get
APKs match!, you have successfully verified that the Google Play release matches with your own self-built version of Signal. Congratulations! Your APKs are a match made in heaven!
If you get
APKs don't match!, you did something wrong in the previous steps. See the Troubleshooting section for more info.
Comparing next time
If the build environment (i.e.
Dockerfile) has not changed, you don't need to build the image again to verify a newer APK. You can just run the container again.
If you cannot get things to work, please do not open an issue or comment on an existing issue at GitHub. Instead, ask for help at https://community.signalusers.org/c/development
Some common issues why things may not work:
- some pinned packages in the
Dockerfileare not available anymore and building of the Docker image fails
- the Android packages in the Docker image are outdated and compiling Signal fails
- you built the Docker image with a wrong version of the
- you didn't checkout the correct Signal version tag with Git before compiling
- this guide is outdated
- you are in a dream