You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm attempting to verify the signature provided by F-Droid for its APK package, but OpenKeychain does not recognize a valid signature in the .asc file, while the Linux desktop GnuPG does.
Download the APK package, then its signature with the .asc file extension. Note that, at least on Android, the file extension will be renamed to .key, with no changes to its content.
Use "Open With" on the signature (.asc file) and choose to "Decrypt with OpenKeychain".
Screen recording on Android:
screen-20240328-143755.mp4
Terminal output on Linux desktop:
$ gpg --verify F-Droid.apk.asc
gpg: assuming signed data in 'F-Droid.apk'
gpg: Signature made Sat 22 Jul 2023 08:48:28 AM -03
gpg: using RSA key 802A9799016112346E1FEFF47A029E54DD5DCE7A
gpg: Good signature from "F-Droid <admin@f-droid.org>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 37D2 C987 89D8 3119 4839 4E3E 41E7 044E 1DBA 2E89
Subkey fingerprint: 802A 9799 0161 1234 6E1F EFF4 7A02 9E54 DD5D CE7A
Your Environment
Android Version: 13
Device Model: Motorola Moto G32 (arm64)
OpenKeychain Version: 6.0.4 (60400)
From Google Play or F-Droid?: Google Play
The text was updated successfully, but these errors were encountered:
I'm attempting to verify the signature provided by F-Droid for its APK package, but OpenKeychain does not recognize a valid signature in the .asc file, while the Linux desktop GnuPG does.
Links:
Here's the signature data:
Steps to Reproduce (for bugs)
.asc
file extension. Note that, at least on Android, the file extension will be renamed to.key
, with no changes to its content.Screen recording on Android:
screen-20240328-143755.mp4
Terminal output on Linux desktop:
Your Environment
The text was updated successfully, but these errors were encountered: