21–30 of 301 posts
I thought the closed-garden app stores were supposed to protect us from this sort of thing?
What good is all the app vetting and sandbox protection in iOS (dunno about Android) if it doesn't really protect me from those crappy apps...
Has anyone tried to compile a list of software that uses these libraries? It would be great to know what apps to avoid
I have some success in catching most of them at https://visitorquery.com
Checked my connection via VPN by Google/Cloudflare WARP: "Proxy/VPN not detected"
> So if you as an app developer include such a 3rd party SDK in your app to make some money — you are part of the problem and I think you should be held responsible for delivering malware to your users, making them botnet members. I suspect that this goes for many different SDKs. Personally, I am really, really sick of hearing "That's a solved problem!", whenever I mention that I tend to "roll my own," as opposed to…
That may be true but I think you're missing the point here. The "network sharing" behavior in these SDKs is the sole purpose of the SDK. It isn't being included as a surprise along with some other desirable behavior. What needs to stop is developers including these SDKs as a secondary revenue source in free or ad-supported apps.
Doubt it. This is just one -of many- carrots that are used to entice developers to include dodgy software into their apps.
The problem is a lot bigger than these libraries. It's an endemic cultural issue. Much more difficult to quantify or fix.
I thought the closed-garden app stores were supposed to protect us from this sort of thing?
I thought the closed-garden app stores were supposed to protect us from this sort of thing?
I thought the closed-garden app stores were supposed to protect us from this sort of thing?
Once again this demonstrate that closed gardens only benefit the owners of the garden, and not the users. What good is all the app vetting and sandbox protection in iOS (dunno about Android) if it doesn't really protect me from those crappy apps...
> So if you as an app developer include such a 3rd party SDK in your app to make some money — you are part of the problem and I think you should be held responsible for delivering malware to your users, making them botnet members. I suspect that this goes for many different SDKs. Personally, I am really, really sick of hearing "That's a solved problem!", whenever I mention that I tend to "roll my own," as opposed to…
Brings a new meaning to dependency injection.
How is this not just illegal? Surely there’s something in GDPR that makes this not allowed.