mirror of
https://gitlab.com/fdroid/fdroidserver.git
synced 2024-11-04 22:40:12 +01:00
8776221988
If working with a random grabbag of APKs, there can be all sorts of issues like corrupt entries in the ZIP, bad signatures, signatures that are invalid since they use MD5, etc. Moving these two checks later means that the APKs can be renamed still. This does change how common.getsig() works. For years, it returned None if the signature check failed. Now that I've started working with giant APK collections gathered from the wild, I can see that `fdroid update` needs to be able to first index what's there, then make decisions based on that information. So that means separating the getsig() fingerprint fetching from the APK signature verification. This is not hugely security sensitive, since the APKs still have to get past the Android checks, e.g. update signature checks. Plus the APK hash is already included in the signed index. |
||
|---|---|---|
| .. | ||
| extra | ||
| getsig | ||
| gnupghome | ||
| metadata | ||
| repo | ||
| signindex | ||
| source-files | ||
| stats | ||
| androguard_test.py | ||
| build.TestCase | ||
| common.TestCase | ||
| complete-ci-tests | ||
| config.py | ||
| description-parsing.py | ||
| dump_internal_metadata_format.py | ||
| import_proxy.py | ||
| import.TestCase | ||
| index.TestCase | ||
| install.TestCase | ||
| keystore.jks | ||
| metadata.TestCase | ||
| org.dyndns.fules.ck_20.apk | ||
| run-tests | ||
| update.TestCase | ||
| urzip-badcert.apk | ||
| urzip-badsig.apk | ||
| urzip-release-unsigned.apk | ||
| urzip-release.apk | ||
| urzip.apk | ||