That way all it will take to infect my parents’ phones with malware capable of scraping copious amounts of my data will be normal phone usage that Apple can’t protect against!
Um… What? iPhone apps run in a sandbox. They can’t access anything. They can’t even run at all unless the user launches the app or interacts with a notification. Background running is strictly limited to things like music playback with very few exceptions (exceptions which are taken away if the user never launches the app).
And for the record, I don’t own an android phone and never have.
Specifically it limits what APIs can and can’t be used by apps and forces the use of entitlements to access features of the hardware.
Downvote if you want, but entitelements are part of the code signing process which this article is trying to avoid. And jailbroken apps already don’t have the protections you’re talking about.
It’s not uncommon for people to datamine not public API all over Apple’s frameworks and the only thing preventing the usage is App Store policies and static analysis tools.
Umm… no? The phone operating system (iOS) enforces sandboxing. You can not run anything outside the sandbox without some exploit, at which point we have a completely new discussion.
Look up code signing and entitlements. This is a compile-time thing and an App store validation thing.
Regardless, what are you even arguing?
All of the sandboxing and entitlements stuff boils down to asking the user for permissions to access the data I described.
An app designed to look exactly like Facebook or Tik-tok, installed from a nefarious or less secure app store would reasonably expect to access contacts, the mic and camera, the username and password for that app, and a lot of other data that it can send to a server and use in ways that will negatively affect lots of people.
Um… What? iPhone apps run in a sandbox. They can’t access anything. They can’t even run at all unless the user launches the app or interacts with a notification. Background running is strictly limited to things like music playback with very few exceptions (exceptions which are taken away if the user never launches the app).
And for the record, I don’t own an android phone and never have.
…do you know what enforces all of that?
The App store…
Specifically it limits what APIs can and can’t be used by apps and forces the use of entitlements to access features of the hardware.
Downvote if you want, but entitelements are part of the code signing process which this article is trying to avoid. And jailbroken apps already don’t have the protections you’re talking about.
It’s not uncommon for people to datamine not public API all over Apple’s frameworks and the only thing preventing the usage is App Store policies and static analysis tools.
Umm… no? The phone operating system (iOS) enforces sandboxing. You can not run anything outside the sandbox without some exploit, at which point we have a completely new discussion.
Look up code signing and entitlements. This is a compile-time thing and an App store validation thing.
Regardless, what are you even arguing?
All of the sandboxing and entitlements stuff boils down to asking the user for permissions to access the data I described.
An app designed to look exactly like Facebook or Tik-tok, installed from a nefarious or less secure app store would reasonably expect to access contacts, the mic and camera, the username and password for that app, and a lot of other data that it can send to a server and use in ways that will negatively affect lots of people.