Android Permission Determination via Shared User Identifier Search
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The Android system's mechanism for shared user identifiers allows newly installed applications to share permissions with existing applications, leading to a risk of increased security vulnerabilities as users are not informed of the permissions being added, thereby compromising system security.
Innovation Solution
A method and apparatus that determine an application's permission by searching for existing applications with the same shared user identifier, allocating a new identifier if necessary, and managing permissions to prevent unauthorized access, ensuring that users are informed of potential risks during installation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the Android system allows applications to share user identifiers and permissions automatically, then application functionality and user experience are improved, but system security deteriorates because users are not informed of permission risks
Solution Approach 1:
The system introduces a feedback mechanism by notifying users of permission sharing risks before installation completes. The risk notification dialog provides users with information about which permissions will be shared, enabling informed decision-making. Users can choose to proceed or cancel based on this feedback, thus maintaining security while preserving functionality.
Solution Approach 2:
The system applies preliminary anti-action by preemptively warning users about potential security risks before the permission sharing actually occurs. The risk notification is displayed during the installation process, allowing users to take preventive action (cancel installation) before the harmful effect (unauthorized permission access) takes place.
2Ease of operation
If the system extracts and adds all permissions from new applications to existing applications sharing the same user identifier, then permission sharing objective is achieved, but security vulnerabilities increase as users cannot learn about added permissions
Solution Approach 1:
The system performs preliminary action by extracting and analyzing permission information from the new application before completing the installation. The risk notification dialog is prepared in advance with specific permission details, allowing users to understand what permissions will be shared before making their decision. This preliminary information gathering enables informed user choice while maintaining the permission sharing functionality.
3Productivity
If the system allows background download and installation of application plugins, then user convenience is improved, but security control deteriorates because users cannot assess permission risks
Solution Approach 1:
The system maintains installation efficiency by allowing background downloads to proceed, but introduces security control through feedback mechanism. When installation is about to complete, the system pauses to display a risk notification dialog with permission information. This feedback loop allows users to review permissions before final installation, balancing efficiency with security control.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Embodiments of the present invention provide a method and an apparatus for determining a permission of an application program. The method for determining a permission of an application program in the present invention includes: receiving an installation request of a first application, where the installation request carries a first permission list that the first application applies for and a first shared user identifier requested by the first application; searching, according to the first shared user identifier, for at least one second application that uses the first shared user identifier and is already installed in a system; and if the first application is a plug-in of the second application already installed in the system, determining a permission of the first application according to the first permission list that the first application applies for and a permission in a second permission list corresponding to the first shared user identifier. The embodiments of the present invention make an application unable to add a permission of the application by adding a plug-in, lowering a risk of a system and improving security of the system.