Feature #2593
UI to communicate when two APKs that should be the same are not
| Status: | In Progress | Start date: | 11/21/2013 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | integrated audit and user-generated data | |||
| Component: |
Description
When a Bazaar APK audit finds two APKs with matching package names and versions but are not perfect matches of each other, it should present this information to the user in a useful way. It should include information as well as easy ways to trigger actions to take to improve the situation (uninstall APK, "freeze" APK, query online data sources, etc)
Related issues
History
#1 Updated by hans about 4 years ago
- Target version changed from 0.2 - ChatSecure/Bluetooth to improved security/usability
#2 Updated by hans about 4 years ago
- Priority changed from Normal to High
#3 Updated by pd0x almost 4 years ago
- Status changed from New to In Progress
#4 Updated by hans over 3 years ago
I don't remember exactly what, but we were discussing something at the last scrum about wanting the info about the installed apps in the FDroid database. It seems that @pserwylo has made FDroid now add the installed apps to the FDroid database by default:
#5 Updated by hans over 3 years ago
one option is to check virustotal.com for their virus scan info. They have a public API:
https://www.virustotal.com/en/documentation/public-api/
It requires an API key, which is tied to a user login. We could include one by default, but that might rapidly overwhelm the virustotal rate limiting. That might violate the terms of service too.
#6 Updated by hans over 2 years ago
- Target version changed from improved security/usability to integrated audit and user-generated data