Is it really possible for app developers to leave out permissions in the list of requested permissions on Google Play and then get them nevertheless when the app is actually installed?
See my other reply for a more lengthy description: https://news.ycombinator.com/item?id=30126488
For other products the accountability is always on the manufacturer/creator of the product - why, in software, do you all demand that big tech censors and polices what you're allowed to consume instead of actually punishing the wrongdoers who created malicious and dangerous software? Why can they just get away with zero accountability and you don't even spare a millisecond of thought?
Whether they are actually legally set up that way (or not) I don’t know. I did go down this rabbit hole 10-15 years ago to do something similar with a lawyer.
What could be interesting is if some states/countries have limits on the fees a money transmitter can charge and an app company sued for them operating illegally.
0: https://www.retailcustomerexperience.com/news/investor-blog-... (the original marketwatch article is unavailable).
Yes, or even just defective. Chain of commerce product liability is well established.
Why should software be different?
I’d encourage you to do it without insulting the other participants on HN.
Spare a millisecond of thought for how your tone shapes the culture here.
But yeah, I think making corps accountable would be of great benefit to IT, if we start hitting them in the wallet I guess that's the only way to make security escape conferences and make it to software companies HQs
I get to pay a corp to get a shitty product that makes me subject all sort of security issue, without being able to blame it on anyone, and in the end I have also to pay with my time because manager X didn't think that it was important to deliver a safe product. So yeah, I want to be paid for the time I have to spend to fix corps shits
Actually, I'm pretty sure there has been some stuff that Microsoft signed, for which MS is paid (not 30% sure), that were malwares. But I'm too lazy to find it
Then again, taking the thought experiment of your comment as written, can a malware dev sue M$ for Windows Defender blocking and/or removing their software?
Also, "being sued" isn't a very strong litmus test on its own. Anyone can be sued for anything at anytime.
Both provide some minimal level of malware protection but make no guarantees and rely on users to scrutinize app sources.
Apple makes somewhat stronger claims of protection so there may be an argument for a higher level of responsibility on iOS and MacOS:
>...users can access these apps on their Apple devices without undue fear of viruses, malware, or unauthorized attacks....
>...all apps are sandboxed—to provide the tightest controls...
>...helps to ensure that these apps are free of known malware...
>...macOS includes state-of-the-art antivirus protection to block—and if necessary remove—malware. [0]
I'm still not sure that a claim of legal liability would hold up in court though.
[0] https://support.apple.com/guide/security/app-security-overvi...
And yes, I think MS should be responsible for apps they are selling. Aswell as Apple or Google.
Hiding behind adds and pretending it is no a proper sale and that they are mediators or whatever is BS.
You're saying they should be responsible. Ethically? Legally? I'm not sure which you mean, but probably both.
That's not the question I was answering though. That question didn't specify the flavor of responsibility, and I chose to answer it from a mostly legal perspective, which is that as things stand they are probably, mostly, not liable.
Traditional retail liability is probably the best place to look in this case. A store can be liable for the products it sells, but if it makes reasonable efforts to determine product safety then those are difficult cases to win unless you can show that the retailer knew, or should have known, that the product was defective or unsafe. One black & white example of that liability would be selling alcohol to underage kids who did not present any ID, or gave a fake ID.
I think "reasonable precautions" is probably the best rule from a practical standpoint. But I'm not otherwise going to address where the line should be drawn on "reasonable" precautions. That's a complex question, individual examples and product classes would vary, and there are plenty of expensive court cases that have not yet produced a universal "bright line" standard for defining "reasonable" precautions.
Google Play hides some permissions on its own, but very basic one (like the one allowing access to internet). That's it.
The dangerous permissions mentioned in the article need to be manually enabled by the user, after installing the application.