Closed Jakeler closed 10 months ago
oliver-steinbrecher
commented
2 years ago We've planed to implement a gallery import (image/pdf) but this has been postponed in favor of other topics. The other approaches are not planed or taken into further considerations.
ingowerren
commented
10 months ago In 2021, the European Union introduced the digital COVID certificate as an EU-wide recognised proof of vaccination, recovery or negative testing for COVID-19. This regulation expired on 30 June 2023. On a transitional basis, the EU will continue to operate the technical systems to enable cross-border certificate checks until 31 December 2023. The transitional operation will end on that date. In Germany, the possibility of issuing digital COVID certificates such as vaccination and recovery certificates will therefore be discontinued on 31 December 2023. The CovPass app and the CovPassCheck app will therefore also be discontinued. The CovPass app will be switched to wallet mode, where the stored certificates will be retained.
What does this mean for you? All functionalities will continue to beavailable until 31 December 2023.
From 1 January 2024:
Support for the app will no longer be offered.
Avoid duplicates
Current Implementation
The App apparently utilizes android keystore APIs, which often use secure hardware to store the secrets, this makes it very hard to extract data. While this is good under normal operation, this also makes it practically impossible to create working backups.
Usual root backup tools like OAndBackupX or TitaniumBackup can only restore normal app data. The restored app crashes immediately with:
Expand crash log
``` 11-11 18:46:21.294 614 614 E KeyMasterHalDevice: Finish send cmd failed 11-11 18:46:21.294 614 614 E KeyMasterHalDevice: ret: 0 11-11 18:46:21.294 614 614 E KeyMasterHalDevice: resp->status: -30 11-11 18:46:21.294 29851 29851 W b : encountered a potentially transient KeyStore error, will wait and retry 11-11 18:46:21.294 29851 29851 W b : javax.crypto.AEADBadTagException 11-11 18:46:21.294 29851 29851 W b : at android.security.keystore.AndroidKeyStoreCipherSpiBase.engineDoFinal(AndroidKeyStoreCipherSpiBase.java:517) 11-11 18:46:21.294 29851 29851 W b : at javax.crypto.Cipher.doFinal(Cipher.java:2113) 11-11 18:46:21.294 29851 29851 W b : at j3.b.c(Unknown Source:32) 11-11 18:46:21.294 29851 29851 W b : at j3.b.b(Unknown Source:0) 11-11 18:46:21.294 29851 29851 W b : at f3.i.c(Unknown Source:11) 11-11 18:46:21.294 29851 29851 W b : at f3.i.j(Unknown Source:9) 11-11 18:46:21.294 29851 29851 W b : at j3.a$b.e(Unknown Source:6) 11-11 18:46:21.294 29851 29851 W b : at j3.a$b.f(Unknown Source:0) 11-11 18:46:21.294 29851 29851 W b : at j3.a$b.d(Unknown Source:11) 11-11 18:46:21.294 29851 29851 W b : at a1.a.b(Unknown Source:50) 11-11 18:46:21.294 29851 29851 W b : at a1.a.a(Unknown Source:4) 11-11 18:46:21.294 29851 29851 W b : at n6.f.a(Unknown Source:36) 11-11 18:46:21.294 29851 29851 W b : at n6.f.b(Unknown Source:13) 11-11 18:46:21.294 29851 29851 W b : at n6.a.Suggested Enhancement
There are multiple possible solutions. Most convenient option would be to have a switch that disables Android keystore encryption and just saves the certificates in normal app data. Android app data already has a quite high security level (Linux permissions and SELinux). Corona-Warn-App does it like this, going even further seems overkill to me. Another idea would be to include a export/import feature in the app. If we consider the "save as EU pdf" as export then it is already half implemented. Only part missing is a import from pdf, like suggested in #20.
Expected Benefits
One part of security is availability and backups are essential to achieve it. Also having a backup option would make it more convenient to always have the certificates when often switching devices.