Project *Core Apps » Bazaar » ChatSecure:Android » KeySync » Orbot » Orfox Private Browser » Orweb » Secure ReaderCacheWordIOCipherNetCipherPanicTrusted Intents » CheckeyLibreoSpideyStoryMaker™SecureSmartCam » CameraV (InformaCam Project) » ObscuraCam
Tracker *Bug Feature Task
Subject *
Description When FDroid client finds that an update has a different signing key, like when FDroid is trying to update an APK installed via Google Play, it should walk the user through actions they can take, like ignoring future updates. Ideally, it would be able to check the signature from the Google Play APK to provide better context to the user for decision making. maybe https://androidobservatory.org or something like that can provide info like that.
Status *New
Priority *Low Normal High Urgent Immediate
Assignee << me >>carriestienshansn8fr8pd0xpserwylorosavitriolixAnonymous
Target version Integrate Kerplapp into FDroid new unified Downloader infrastructure convert FDroid to appcompat-v7 implement swap UI integrated audit and user-generated data swap repos with Bluetooth and Bonjour
Start date
Due date
Estimated time Hours
% Done0 % 10 % 20 % 30 % 40 % 50 % 60 % 70 % 80 % 90 % 100 %
Component
Files (Maximum size: 195 MB)