Re:Apple starts rejecting apps with “hot code push” features
by edude03 on Wednesday March 08, 2017 @11:32AM
(#13821328)
This is a great idea actually. Actually, isn't google already doing this via SELinux? You give the app a manifest of calls it's allowed to make, and if the call isn't in the manifest the call gets rejected?
Re:Apple starts rejecting apps with “hot code push” features
by AstralStorm on Thursday March 09, 2017 @05:38AM
(#13828409)
SELinux is not that strong. It works on kernel syscall boundaries and some parameters thereof, and those aren't particularly fine grained. Service access is governed by a separate Google API, for example.
Moreover, any random app cannot enhance SELinux policy of the system.
Re:Apple starts rejecting apps with “hot code push” features
by leonatan on Thursday March 09, 2017 @03:22AM
(#13827913)
There are many legitimate uses of calling methods and functions using reflection. Expecting to hit all of them in a short review process is comically optimistic for anything but the simplistic of apps.
Your suggestion of enforcing this also makes no sense from performance or privacy standpoint.
At runtime, any API calls made by the app are checked against this file; if a new API call is found, then it must have escaped Apple's code scanning logic. The API call can be rejected and logged for Apple to improve their scanner.