German Corona App without proprietary Google libraries
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 

2.4 KiB

How to rebuild Corona Contact Tracing Germany

The CCTG app can be built reproducibly. This means that you can re-run the build instructions and arrive at the very same binary that we publish[1].

The upstream CWA build is currently not reproducible because of non-deterministic android vector graphics -> png generation. In CCTG we instead pre-generated all pngs and included them into the source tree. This was easily done by running the build once and copying all png files under /build into /src/main/res/drawable-XXXXX.

You can recreate the build by using the following docker container. The docker build system is mostly provided for convenience. Rebuilds should work with fdroid build -l de.corona.tracing on any properly configured build system[2].

cd docs
docker build -t cctg-builder .
docker run -it --volume ${PWD}/repo:/repo cctg-builder

After that you should have the latest apk in ./repo

[1] Android apks are signed with an embedded signature. This means the final apk has to be reproduced with some trickery as a rebuilder is not in possession of the private key to re-generate the signature. Currently this works by recreating an unsigned build, transplanting signature of the apk to-rebuild and then verifying this signature on the newly assembled apk. If this passes, the apk is identical and we can publish it.[3]

[2] The docker build uses an experimental fdroidserver version which is able to automatically download the Android NDK dependency as well as generally having better defaults. In general you'll need:

  • some recent fdroidserver version
  • openjdk-8 (newer version might work, but weren't tested)
  • Android NDK version r21c
  • Android SDK (at least the cmdline-tools, the rest will be downloaded on-demand)
  • the de.corona.tracing.yml metadata file

[3] There's, unfortunately, more to this. The procedure described above works with Android signatures v1 (which are basically .jar signatures) but is not yet implemented for v2-v4 signatures. F-Droid instead continues to verify the v1 signature and if that succeeds publishes the original apk.