Abstract
Android has robust system that prevents malware from damage to sensitive data and abusing system resources. The core element of that system is a permission subsystem, which allows restricting access to system resources and private data. Each application requests a permission for correct work and user gives it or cancel installation process. This article describes one of its drawbacks: it is impossible to set optional permissions. The paper also partially considers a modified Android permission subsystem, which allows more flexible approach to set application permissions. There is also a description of a way to integrate existing applications into the modified Android version without sacrificing of flexibility. The approach is based on mocking certain resource for a certain application. Thus, an application deals with a mock resource and can’t understand if this resource is mock or real. On the one hand, this approach allows an application to work with any resource like with a genuine one; on the other hand, it protects sensitive data from unauthorized access. This approach can be used in future Android OS versions to improve application permissions enforcement.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callMore From: International journal "Programmnye produkty i sistemy"
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
