3 ms·
The main repository also signs everything with f-droid keys, not the original developer's. This means any compromise in f-droid compromises everything.
by sneak 6y ago
The main repository also signs everything with f-droid keys, not the original developer's. This means any compromise in f-droid compromises everything.
- khimaros 6y agosounds like a problem to solve. build in both places, verify build hashes agree, upstream dev infra signs and sends signed build to f-droid, f-droid verifies hash against its own build, verifies upstream signature, signs and then lists. apks can have more than one signature.
- khimaros 6y agoactually, it turns out this is no longer a limitation: https://f-droid.org/docs/Reproducible_Builds/ https://f-droid.org/docs/Reproducible_Builds/ "Publishing signed binaries from elsewhere (e.g. the upstream developer) is now possible after verifying that they match ones built using a recipe. Publishing only takes place if there is a proper match."