|
|
|
|
|
by klibertp
3422 days ago
|
|
> I guess you don't use I think he was talking about programming the apps, not just using them. From the looks of it (after reading the comments here and nothing more, so excuse me if I'm completely wrong) it may be a real inconvenience from the dev perspective: I can somehow understand the "no 127.0.0.1 communication" policy, but I expect to communicate with a spawned process via stdin/stdout pipes. |
|
Old style IPC leads to information leaks and is another attack vector.
You cannot do that on Android for example, Google explicitly removed UNIX V IPC from their Linux fork. You are expected to use TCP/IP or Android RPCs, assuming the app has android.permission.INTERNET permission.
Also using fork/exec() on Android isn't a good idea, http://stackoverflow.com/questions/16179062/using-exec-with-...
Which I doubt that would still work on Android 7 by the way.
On iDevices, the same applies.
https://developer.apple.com/library/content/documentation/Se...
So people are complaining about Microsoft adopting what is already best practices on the other desktop/mobile sandbox models.