News for hackers. Stuff that matters.
Re:KDE Connect removed from Google Play store for violating ... by Arnt on Tuesday March 19, 2019 @06:16AM (#19429504)
Speaking as a KDE Connect user who's heard of F-Droid, I installed F-Droid, then deinstalled it. It was too noisy and intrusive. When I told it I didn't want to replace an app with its version it kept asking again and again, every day at least.

Since then I've head that the F-Droid operators insist on signing all apps themselves, instead of the developers' signature. That's as bad as the TLS inteceptors that insist on accepting an extra CA.

Some people seem to think that F-Droid is obviously preferable to Googleplay. That is, at the very least, not obvious.

Re:KDE Connect removed from Google Play store for violating ... by Iolaum on Tuesday March 19, 2019 @06:27AM (#19429549)
Fdroid maintainers require shipped apk's to have 0 non-free components. The only way to ensure that is to build the apps themselves (so that they can verify code and control dependencies). This means that they can only use their own keys.
Re:KDE Connect removed from Google Play store for violating ... by levosmetalo on Tuesday March 19, 2019 @06:44AM (#19429629)
Debian is also signing all Debian packages with in their own repositories with their own keys, and nobody takes this as an issue.
Re:KDE Connect removed from Google Play store for violating ... by Arnt on Tuesday March 19, 2019 @08:16AM (#19430068)
No it doesn't. They could check the developer's signature against an APK built from source. It's not that difficult.

BTW. In my case the app they urged me to replace the stock keyboard with a version that had been built without support for Norwegian. Is the language data in Android non-free?

Re:KDE Connect removed from Google Play store for violating ... by kuschku on Tuesday March 19, 2019 @08:19AM (#19430084)
They can, and they offer that, if the developer supports reproducible builds.

Most apps aren’t possible to be built reproducibly, though, as the Android developer toolkit was never designed for reproducible builds and relies on stuff like filesystem ordering of files (which differs between machines).

Re:KDE Connect removed from Google Play store for violating ... by kuschku on Tuesday March 19, 2019 @08:18AM (#19430074)
You’re even able to ship your own builds signed with your own developer key on F-Droid if F-Droid is able to build the exact same APK themselves.

Reproducible builds are the best option for such a store :)

Re:KDE Connect removed from Google Play store for violating ... by 0815test on Tuesday March 19, 2019 @06:34AM (#19429574)
> Since then I've head that the F-Droid operators insist on signing all apps themselves, instead of the developers' signature.

They do reproducible builds starting from publicly available source. Given the AOSP design where code signatures are mandatory and updates are only allowed if signed by the same key, they're taking the best feasible approach.

Re:KDE Connect removed from Google Play store for violating ... by BubuIIC on Tuesday March 19, 2019 @07:48AM (#19429916)
> When I told it I didn't want to replace an app with its version it kept asking again and again, every day at least.

F-Droid can't replace a version installed form GPlay with it's own version as they are (except a handful) signed with a different key.

It also won't even show you these versions anymore unless you enable an expert settings options.

Re:KDE Connect removed from Google Play store for violating ... by ForHackernews on Tuesday March 19, 2019 @08:14AM (#19430057)
I trust the F-Droid maintainers more than J. Random app developer, honestly.
Re:KDE Connect removed from Google Play store for violating ... by Arnt on Tuesday March 19, 2019 @08:25AM (#19430105)
Care to elaborate? You're trusting the developer to write the source code and do all the debug builds, what's the problem with building the production build?
Re:KDE Connect removed from Google Play store for violating ... by ubercow13 on Tuesday March 19, 2019 @09:14AM (#19430441)
Assuming you trust F-Droid, it eliminates the possibility that the developer isn't using their published source code. eg. they might hide their tracking code from their public github repo but build it into their release apk.