Earlier this year, we reported about our progress concerning reproduciblebuilds. Meanwhile, more and more appsare using this; you can find some statisticsher...
F-Droid used to build and sign the APK for each app they distribute using keys owned by F-Droid
That meant you had to trust F-Droid to distribute the app as per the source, and hope that the source hadn’t been compromised (as the developer wasn’t signing anything)
Now when a new app is added to the repo, they build an APK from source and compare it with an APK distributed by the developer
If they match exactly (and if there is no reason to think the developer key has been compromised) then F-Droid will instead distribute APKs signed with the developer key, and verify that the same key was used for each update
If the same key was used, F-Droid doesn’t need to build the APK themselves but can distribute the update as-is
The advantages then are that F-Droid is acting as an additional layer of security and assurance to the developer signing the APK, and updates can be distributed faster as F-Droid doesn’t have to build them
Yes, that video is primarily complaining about F-Droid self-signing, and that it creates: a requirement to trust them; a single point of failure for security; and slows updates
The trade off is that developers must maintain their key, if they lose it the user must uninstall and reinstall the app, as Android will not trust an update signed with a different key
What alternative does the video promote? Trusting Google and the Playstore? Trusting each dev of every app to deliver apks which match the code? I don’t want to give the video more clicks if it’s scaring away people from F-droid towards worse alternatives.
No need to click, it complains about exactly what has now been changed. In essence you are always trusting the dev, why add other parties to that chain
deleted by creator
F-Droid used to build and sign the APK for each app they distribute using keys owned by F-Droid
That meant you had to trust F-Droid to distribute the app as per the source, and hope that the source hadn’t been compromised (as the developer wasn’t signing anything)
Now when a new app is added to the repo, they build an APK from source and compare it with an APK distributed by the developer
If they match exactly (and if there is no reason to think the developer key has been compromised) then F-Droid will instead distribute APKs signed with the developer key, and verify that the same key was used for each update
If the same key was used, F-Droid doesn’t need to build the APK themselves but can distribute the update as-is
The advantages then are that F-Droid is acting as an additional layer of security and assurance to the developer signing the APK, and updates can be distributed faster as F-Droid doesn’t have to build them
deleted by creator
Yes, that video is primarily complaining about F-Droid self-signing, and that it creates: a requirement to trust them; a single point of failure for security; and slows updates
The trade off is that developers must maintain their key, if they lose it the user must uninstall and reinstall the app, as Android will not trust an update signed with a different key
What alternative does the video promote? Trusting Google and the Playstore? Trusting each dev of every app to deliver apks which match the code? I don’t want to give the video more clicks if it’s scaring away people from F-droid towards worse alternatives.
No need to click, it complains about exactly what has now been changed. In essence you are always trusting the dev, why add other parties to that chain