For one thing, it fundamentally relies on breaking the signature-based security model by allowing microG to falsely pass signature checks.
-
-
Replying to @CopperheadOS @RichFelker
They never changed their required OS patch to reduce the scope of the signature faking to make it less of a security hole.
2 replies 0 retweets 0 likes -
Replying to @CopperheadOS @RichFelker
That isn't a single issue either. It's representative of the project as a whole. Pointed out a similar issue with network-based location.
1 reply 0 retweets 0 likes -
Replying to @CopperheadOS
I think it's representative of having a model aligned with my needs and not yours.
1 reply 0 retweets 0 likes -
Replying to @RichFelker
The model of depending on Google and then getting wiped out when they crack down on piracy and use of their services without permission?
2 replies 0 retweets 0 likes -
Replying to @CopperheadOS
I'm not wasting time repeating this conversation. At this point you're being disingenuous.
2 replies 0 retweets 0 likes -
Replying to @RichFelker @CopperheadOS
You have a fundamental belief in the legitimacy of Google's control in this area. I don't. Let's leave it at that.
1 reply 0 retweets 0 likes -
Replying to @RichFelker
No, have a fundamental belief that piracy and using Google's APIs against their terms of use is not a way to escape from Google control.
1 reply 0 retweets 1 like -
Replying to @CopperheadOS @RichFelker
Implementing the Google Play Services APIs when possible without depending on Google is much different than what microG does.
2 replies 0 retweets 0 likes -
Replying to @CopperheadOS
Many of the apis they offer are fake/stubbed just to get apps that don't really need them to run.
2 replies 0 retweets 0 likes
GCM is obvious exception and there's no way around it if the app depends on a network service only accessible through GCM.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.