Android Permission Certificate for High-Risk Access Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The Android operating system's current permission architecture grants high-risk permissions to third-party applications when they are re-signed as system applications, violating the least-privilege principle and allowing unnecessary access to sensitive APIs.
Innovation Solution
A system and method that manage the installation of Android application packages by issuing specific, device-specific high-risk permissions through a permission certificate, ensuring only requested permissions are granted and preventing misuse by verifying cryptographic signatures with the device manufacturer's public key.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If third-party applications are re-signed as system applications to grant high-risk permissions, then the applications can access protected APIs, but the least-privilege principle is violated and unnecessary access to sensitive APIs is allowed
Solution Approach 1:
The patent segments the permission granting process by introducing a separate permission certificate that is distinct from the application signature. Instead of re-signing the entire application as a system application, the system issues a dedicated permission certificate that grants specific high-risk permissions. This segmentation allows third-party applications to access protected APIs without being treated as system applications, thereby maintaining the least-privilege principle while enabling necessary functionality.
Solution Approach 2:
The patent introduces a permission certificate as an intermediary mechanism between the application and the protected APIs. This permission certificate acts as a mediator that verifies and grants specific permissions without requiring the application to be re-signed as a system application. The permission certificate contains cryptographic signatures that authorize access to specific protected APIs, thereby enabling controlled access while maintaining security boundaries.
2Reliability
If a permission certificate with cryptographic signature verification is implemented, then security is enhanced and misuse is prevented, but the installation process becomes more complex
Solution Approach 1:
The patent implements preliminary action by pre-generating permission certificates with cryptographic signatures before the application installation process. The permission certificate is created in advance with the necessary cryptographic verification mechanisms already in place. During installation, the system simply verifies the pre-existing cryptographic signature rather than performing complex real-time permission evaluation, thereby enhancing security while minimizing the complexity added to the installation process.
Data Source
AI summary
This application discloses a mobile device and method for managing installation of an application package (APK) in the mobile device. The device receives an installation request for installing the APK. The device retrieves a permission certificate for the APK according to the installation request. The permission certificate includes a cryptographic signature. The device determines validity of the permission certificate by verifying the cryptographic signature included in the permission certificate using a permission certification public key provided by a manufacturer of the device. The permission certification public key is stored in the device. The installation of the APK in the device is allowed when the permission certificate is determined to be valid. Using the method, the APK requires the device to grant specific high-risk permissions to the application upon installation.