Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

signed #1054

Open
patatetom opened this issue May 24, 2024 · 3 comments
Open

signed #1054

patatetom opened this issue May 24, 2024 · 3 comments
Labels

Comments

@patatetom
Copy link

hi,
how and on what basis can I verify the signature of the APK archive provided on GitHub ?
in other words, how can I verify that the APK archive really comes from gouv.fr ?
regards, lacsaP.

@yostyle
Copy link
Contributor

yostyle commented May 29, 2024

Hi @patatetom,

You can verify the checksum files. All signatures are stored in checksums.txt from assets.

If you prefer, I can send you the signatures on Tchap if you already have an account.

@patatetom
Copy link
Author

I was thinking more of private/public key (eg. "signed") than file checksum.

@yostyle
Copy link
Contributor

yostyle commented May 30, 2024

All APKs are signed with the same key. You can compare them with this certificate signature :
Signer #1 certificate SHA-256 digest: 2799b5dc1c4ee23127bffdad325db7096f5d0b4e3856f0000305e23f61f991ac
Signer #1 certificate SHA-1 digest: 48d2a6cb6a779fc8fa3b75cd56a55cc706886205
Signer #1 certificate MD5 digest: e1ab53bee87938be161dbdce0876a713

You should use android build tools to get this information from APKs: apksigner verify --print-certs gplay-tchap-withdmvoip-withpinning-arm64-v8a-v2.11.6-signed.apk

The private key is not shared. If you need more information please contact the support of Tchap :
support@tchap.beta.gouv.fr.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants