Good news regarding expiring certificates: 2.23.2.0 is available for download on https://bubu1.eu/cctg and supports re-issueance of such certificates.

After installing the update, it may take up to a day before the reissuance option becomes available.

To learn more about the renewal process, please refer to https://www.coronawarn.app/en/blog/2022-06-01-cwa-2-23/.

f-droid.org builds are unfortunately not going to be available until the latest reproducible builds issue is resolved (https://codeberg.org/corona-contact-tracing-germany/cwa-android/issues/265), sorry.

CCTG F-Droid Repo

CCTG F-Droid Repo

Gute Neuigkeiten bezüglich ablaufender Zertifikate: 2.23.2.0 is ab sofort zum Download auf https://bubu1.eu/cctg verfügbar und ermöglicht die Neuausstellung solcher Zertifikate.

Nach Installation des Updates kann es bis zu einem Tag dauern, bis die Neuausstellung in der App verfügbar ist.

Weitere Informationen zur Erneuerung von Zertifikaten finden sich hier: https://www.coronawarn.app/de/blog/2022-06-01-cwa-2-23/

CCTG F-Droid Repo

CCTG F-Droid Repo

Die Version auf f-droid.org kann leider erst aktualisiert werden, wenn der neuste Issue zu reproduzierbaren Builds behoben ist (https://codeberg.org/corona-contact-tracing-germany/cwa-android/issues/265/).
2.24 Reproducible build

F-Droid releases got stuck with 2.21 again. From the [F-Droid log](https://f-droid.org/repo/de.corona.tracing_2140101.log.gz): ``` DOES NOT VERIFY ERROR: APK Signature Scheme v3 signer #1: APK integrity check failed. CHUNKED_SHA256 digest mismatch. Expected: <502e4a80a0575b695c6b3050d132d24b7b24094a0e15429901beb90862035c04>, actual: <0ec8a657b0d0ebca73c13b000831835d36737c0058e476c592253dd1ad07ece6> 2022-04-27 05:12:19,034 ERROR: /tmp/tmpzt6w0n_g/sigcp_de.corona.tracing_2210102.apk: 2022-04-27 05:12:19,034 INFO: ...NOT verified - /tmp/tmpzt6w0n_g/sigcp_de.corona.tracing_2210102.apk 2022-04-27 05:12:20,690 DEBUG: > diff -r /tmp/tmpzt6w0n_g/unsigned_binaries_de.corona.tracing_2210102.binary /tmp/tmpzt6w0n_g/_tmp_tmpzt6w0n_g_sigcp_de.corona.tracing_2210102 2022-04-27 05:12:20,924 DEBUG: removing unsigned/de.corona.tracing_2210102.apk 2022-04-27 05:12:20,935 DEBUG: removing unsigned/binaries/de.corona.tracing_2210102.binary.apk 2022-04-27 05:12:21,122 ERROR: Could not build app de.corona.tracing: compared built binary to supplied reference binary but failed ==== detail begin ==== Unexpected diff output: Binary files /tmp/tmpzt6w0n_g/unsigned_binaries_de.corona.tracing_2210102.binary/content/assets/dexopt/baseline.prof and /tmp/tmpzt6w0n_g/_tmp_tmpzt6w0n_g_sigcp_de.corona.tracing_2210102/content/assets/dexopt/baseline.prof differ Binary files /tmp/tmpzt6w0n_g/unsigned_binaries_de.corona.tracing_2210102.binary/content/classes3.dex and /tmp/tmpzt6w0n_g/_tmp_tmpzt6w0n_g_sigcp_de.corona.tracing_2210102/content/classes3.dex differ Binary files /tmp/tmpzt6w0n_g/unsigned_binaries_de.corona.tracing_2210102.binary/content/classes4.dex and /tmp/tmpzt6w0n_g/_tmp_tmpzt6w0n_g_sigcp_de.corona.tracing_2210102/content/classes4.dex differ ==== detail end ==== 2022-04-27 05:12:21,122 DEBUG: Error encoutered, stopping by user request. ==== detail end ==== ``` The situation has not been resolved yet, so no builds for 2.23 were submitted. @klonfish Would you be interested in having a look at this again? A diff of 2.23 would be very helpful, also in spotting the places where we need to apply #135 again.

Codeberg.org
@CCTG Danke, ich drücke die Daumen!
@CCTG Hat zu meiner Überraschung einwandfrei grklappt. Aber wie kann es denn sein, dass die Version aus dem Repo die F-Droid-Version updatet? Normalerweise bekomme ich eine Warnung, dass die Signaturen nicht übereinstimmen und ich die F-Droid-Version erst deinstallieren muss.
@matterharz Bei Apps mit reprodizierbaren Builds lässt sich das einrichten – weil der Build von f-droid.org dann Bit-für-Bit übereinstimmt mit dem Build der Autorenschaft. So kann deren Signatur dann kopiert werden.