CN102981835B - Android application program permanent Root permission acquiring method - Google Patents
Android application program permanent Root permission acquiring method Download PDFInfo
- Publication number
- CN102981835B CN102981835B CN201210436649.9A CN201210436649A CN102981835B CN 102981835 B CN102981835 B CN 102981835B CN 201210436649 A CN201210436649 A CN 201210436649A CN 102981835 B CN102981835 B CN 102981835B
- Authority
- CN
- China
- Prior art keywords
- application program
- executable program
- android
- file
- android application
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Landscapes
- Stored Programmes (AREA)
Abstract
The invention provides an android application program permanent Root permission acquiring method. The method includes the steps of editing operations where Root permission is needed, compiling the operations into an executable program document, containing the executable program document into an application program which is authorized through a one-time subscriber unit (su) program, copying the executable program document to a /system/bin directory, modifying an owner and a group of the executable program document to be a root, and setting the subscriber unit identification (suid) position. As a result, the executable program document can have the Root permission every time the executable program document is executed so as to prevent an authorized window from popping out again. Due to changes of requirements, the executable program document is likely to need upgrading. Therefore, the executable program document needs achieving a self-upgrading function so as to prevent the authorized window from popping out again when upgrading. The android application program permanent Root permission acquiring method executes various operations with the identification of the Root. Even if the application program is reinstalled and upgraded, the su program authorization operation does not need repeating again. Therefore, the android application program permanent Root permission acquiring method brings great convenience to users.
Description
[technical field]
The present invention relates to the application program rights management techniques field on Android system, particularly relate in the Android mobile phone of a kind of Root, Android application program forever obtains the method for Root authority.
[background technology]
In Android android system, third party application carries out running with the identity of casual user, and this just makes the limited authority system of this application program, as application program to access or revise Android system file time, will the failure because of insufficient permission.The Android mobile phone had now has carried out Root setting, and this Root is the super administrator account in the class unix systems such as Linux.For Android phone, usual said Root, be exactly by various method in fact, the su program file of system is copied to/system/bin catalogue under, and SuperUser empowerment management is installed, third party application can perform by su program (su program is rights management file) operation needing Root authority.But the mobile phone of Root setting, can third party application just directly have the operation of Root authority? actually this is not so, on the mobile phone of Root, the file of a su program by name can be deposited under/system/bin catalogue, and SuperUser (empowerment management) application program is installed.Other application programs are wanted to perform with Root authority, and just must perform shell-command by su program, and now, SuperUser will eject mandate dialog box, user must click permission, and order could successfully be performed.When click allows, if do not select " remembeing " option, when so application performs shell-command by su program at every turn, all can eject the dialog box of authorizing and reminding.In addition, if application program updating, even if remembered so before to allow to operate, then when performing shell-command by su program, also again to carry out repetitive endowment by su program.
The dialog box that the mandate of ejecting in addition is reminded can bring following problem: during for the third-party application of user on an interface of mobile phone on operating handset, authorize the ejection not too large problem of frame, because now user look at mobile phone in some operation of execution, user can find to authorize dialog box eject and confirm timely, and just operation is more loaded down with trivial details.But, the operation interface of some application program no longer on mobile phone, but on pc machine, mobile phone is connected to pc machine by user, then managing mobile phone is carried out by pc machine, now, user can't go to pay close attention to mobile phone screen, so, when authorizing dialog box to eject, user just can not Timeliness coverage confirming, and because mobile phone enters screen protection, frame can be authorized to show, so just cause authorization failure.Certainly, user, when first time authorizes, can choose " remembeing " option, and next time just need not authorize again, but application program often can upgrade version, after renewal, re-starts mandate again, bring very big inconvenience to the use of user.
One " the application program method for managing dynamic permission under Android platform " is provided in prior art, see that publication number is: CN102289633A, publication date is: the Chinese patent of 2011.12.21, comprises Dynamic Selection when application program is installed and preserves its own system authority list; After installation, user revises described System Privileges table by man-machine interface Dynamic Selection; When access needs the API of authority, according to the record in the System Privileges table of this application program, Android platform judges whether that this API is disabled; When described API is disabled, whether this application program selects amendment by man-machine interface prompting user; If user selects to revise authority, Android platform allows this application program to access described API, otherwise this application program exits access.This right management method, user can as required and personal experience revise the authority of application program at any time, thus the malice access resources of application program can be prevented to a great extent, the hazardous acts such as amendment, steal personal information.If but when the application program under the method Android platform has a renewal, the rights management of this setting will be lost efficacy, also again configuration to be entered, troublesome poeration.
Here it is to be noted to be easier to understand the present invention:
1, in Linux, the problem of file permission:
File permission: each Linux file has four kinds of access rights: readable (r), (w) can be write, can (x) be performed, lack of competence (-).
Authority is classified: the owner, group membership, other users.The authority of every class can use letter representation, as rwxrwxr-x represents: namely the owner and group membership have the authority of reading and writing, execution, other users only have authority (i.e. rwx ' the owner ' rwx ' group membership reading and perform ' other users of r-x ' ').Digital representation: so-called digital representation, refer to and r, w and x are represented with 4,2,1 respectively, what do not have granted rights (-) is then 0, then authority is added, as follows: file permission is rwxr-xr-x, be converted to numeral for (421) (401) (401), after addition, be expressed as 755.
2, Linux user and grouping:
Linux is a multi-task and multi-user operating system.
Multitask: multiple foreground application and background service program macroscopically while run.
Multi-user: multiple user is login system operation simultaneously; For ensureing the privacy of user and the protection of setting up and restriction scheme.
A power user is all there is in common multi-user system, such as, root user in Linux, administrator etc. in Windows system, other users that several have different authority classification grades can be there are in system, the domestic consumer etc. such as set up by power user, Linux distribution version all requires to set up a domestic consumer when mounted mostly at present, and uses this user to log in.
3, user's group:
Can divide into groups to user, user's group can comprise multiple user, and a user also can belong to multiple grouping simultaneously.
Such as, following grouping and user is had:
Grouping group1, comprises user user1, user2
Grouping group2, comprises user user2
Create a file f by the user1 in group1 now, specify its authority to be 775, so user1 and user2 has the authority of reading and writing, execution to file f, the authority that the user2 in group2 then only reads and performs
4, the flag suid in system:
Suid is the meaning of Set User ID
If a file has been set up suid flag, can execute bit can performing on the position of (x) of possessory authority can be shown, such as:
Rwsr-xr-x represents in the possessory authority in suid and authority classification and can execute bit be set up.
The numeral that digital representation: suid is corresponding is 4, as rwsr-xr-x is just expressed as 4755
The effect of suid: allow when originally not having the user of corresponding authority to run this program, can access resource that he does not have authority to access (what namely allow some resources not have access rights has had access rights).
Such as, user user1 and user2 is had; Create an ordinary file f by user user1 now, its authority is rwxr-xr-x (755), and create an executable file r, and its authority is rwxr-xr-x (not arranging suid), now by user2 working procedure r, the validated user id (euid) of r is exactly user2, because user2 is to the unwritten authority of file f, so r program also just cannot revise file f; If be provided with the suid of file f, namely authority changes rwsr-xr-x (4755) into, now will be set to its possessory id, i.e. user1 by the euid of user2 working procedure r, r again, and also just can revise file f.
[summary of the invention]
The technical problem to be solved in the present invention, is to provide a kind of Android application program forever to obtain the method for Root authority, and when it solves application program with Root identity fill order, SuperUser repeatedly can eject the problem of authorizing and reminding.
The present invention is achieved in that a kind of Android application program forever obtains the method for Root authority, comprises the steps:
Step 1, will the operation of using Root authority in Android application program, be needed to be write by C/C++ language, and be compiled into an Android system executable program file, and the function of described executable program file energy teaching display stand upgrade function and the communication with Android application program; Executable program file is packaged in Android application program;
Step 2, under Android system judgement/system/bin catalogue under whether there is described executable program file, no, then enter step 3; Be then judge that executable program file is the need of upgrading, upgrade, then Android application program is set up with this executable program file and is communicated, and calls self-upgrade function, carries out upgrading processing, and proceed to step 8 to this executable program file; Do not upgrade, then directly enter step 8;
The su program that step 3, Android application program run Android system carries out first time mandate to operation user;
Step 4, by Android system /system catalogue carries out weight carry for can write state;
Step 5, by Android system /authority of system/bin catalogue arranges, with ensure Android application program right/catalogue of system/bin has the authority write;
Step 6, described executable program file copied to described/system/bin catalogue under, and revise the owner of this executable program file authority classification and be affiliatedly grouped into Root;
Step 7, arrange the suid flag of executable program file, after arranging suid flag, namely executable program file just with possessory identity performed by Android application program, can have the operation of Root authority;
Step 8, Android application program perform executable program file and communicate with its foundation, as long as now Android application program needs the operation of using Root authority to be undertaken performing by executable program file, carry out repetitive endowment without the need to the su program by Android system.
Tool of the present invention has the following advantages: the present invention writes needing the operation of using Root authority, and be compiled into an executable program file, this executable program file is carried out dispose, arrange, this file can be made so at every turn to perform and all to have Root authority, thus avoid again ejecting mandate frame.Due to the variation of demand, this file routine may need upgrading, therefore the file function that needs teaching display stand upgrade, to avoid needing again to eject mandate frame during renewal.The present invention performs various operation by this file with the identity of Root, even if application program is reset, upgraded, also without the need to carrying out the su program authorization operation of repetition again, brings great convenience to the use of user.
[accompanying drawing explanation]
Fig. 1 is the inventive method schematic flow sheet.
[embodiment]
As shown in Figure 1, a kind of Android application program of the present invention forever obtains the method for Root authority, comprises the steps:
Step 1, will the operation of using Root authority in Android application program, be needed to be write by C/C++ language, and be compiled into an Android system executable program file (as, the name of this executable program file is called mySu), and the function of described executable program file energy teaching display stand upgrade function and the communication with Android application program; Executable program file is packaged in Android application program;
Step 2, under Android system judgement/system/bin catalogue under whether there is described executable program file, no, then enter step 3; Be, then judge that executable program file is the need of upgrading, upgrade, then Android application program is set up with this executable program file communicate (borrowing the function having communication in executable program file and Android application program during this communication), and call self-upgrade function, upgrading processing is carried out to this executable program file, and proceeds to step 8; Do not upgrade, then directly enter step 8;
The su program that step 3, Android application program run Android system carries out first time mandate to operation user, it is specially: Android application program runs the su program of Android system, and obtain the output stream of su program, su order afterwards can directly be ordered toward output stream write and perform, and without the need to reruning su program, so just only need subscriber authorisation once, now, output stream toward su program writes an arbitrary character Command, and (this character Command is inessential order, as " id "), this character Command is mainly in order to allow the SuperUser of Android system can eject mandate dialog box, now, the SuperUser of Android system can eject mandate dialog box, operation user clicks permission, then continue to perform described step 4, operation user clicks refusal, then process ends.
Step 4, by Android system /system catalogue carries out weight carry for can write state; It is specially: toward output stream write first order of su program, by Android system /system catalogue carries out weight carry for can write state, this first order is: " mount – o remount – w – t [type] [device]/system ", wherein [type] is the file system type wanting carry, [device] is for wanting the equipment of carry, these two is /the relevant parameter of system catalogue carry, is that the shell-command by performing Android system obtains.
Step 5, by Android system /authority of system/bin catalogue arranges, with ensure Android application program right/catalogue of system/bin has the authority write; It is specially: toward output stream write second order of su program, by Android system /authority of system/bin catalogue changes 777 into, with ensure Android application program right/catalogue of system/bin has the authority write, this second order is: " chmod 777/system/bin ".
Step 6, described executable program file copied to described/system/bin catalogue under, and revise the owner of this executable program file authority classification and be affiliatedly grouped into Root; It is specially: toward output stream write the 3rd order of su program, under executable program file being copied to the catalogue of described/system/bin, 3rd order is " dd if=[fromPath] of=[toPath] ", wherein [fromPath] is the path at executable program file now place, [toPath] path for copying to, the title of namely/system/bin/ executable program file; And order toward the output stream write the 4th of su program, revise the owner of this executable program file authority classification and be affiliatedly grouped into root, 4th order is " title (be " mySu ", this title also can be replaced with other name) of chown root:root/system/bin/ executable program file ".
Step 7, arrange the suid flag of executable program file, after arranging suid flag, namely executable program file just with possessory identity performed by Android application program, can have the operation of Root authority; It is specially: toward output stream write the 5th order of su program, the suid flag of executable program file is set, and be readable execution by executable program file priority assignation, namely executable program file priority assignation is 4755, wherein " 4 " are suid flags, namely executable program file just with possessory identity performed by Android application program, can have the operation of Root authority; Such application program forever can obtain the operation of Root authority; 5th order is: " title (being " mySu ") of chmod 4755/system/bin/ executable program file ".
Step 8, Android application program perform executable program file and communicate with its foundation, as long as now Android application program needs the operation of using Root authority to be undertaken performing by executable program file, carry out repetitive endowment without the need to the su program by Android system.
Wherein, the operation of described Root authority comprises: obtain file directory, mourn in silence installation procedure and Uninstaller etc.
Here it is worth mentioning that:
The difference of carry and heavy carry, carry:
In linux system, need memory device to be mounted to certain catalogue, we normally could use in file management; The then general carry information can seeing each catalogue by performing mount order in shell, such as :/dev/block/mmcblk0p9/system ext4ro; This information represents: memory device "/dev/block/mmcblk0p9 " is mounted to/system catalogue, and its file system type is " ext4 ", and its access limit is " ro " (read-only)
Heavy carry: generally perform remount order by shell and carry out carry memory device again: such as: " mount – o remount – w – t ext4/dev/block/mmcblk0p9/system ", represent the heavy carry of general/system, its file system type is " ext4 ", its memory device is "/dev/block/mmcblk0p9 ", its access limit is "-w ", namely readablely writes.What relate in step 4 is the operation carrying out heavy carry.
In a word, the present invention performs various operation by this file with the identity of Root, even if application program is reset, upgraded, also without the need to carrying out the su program authorization operation of repetition again, brings great convenience to the use of user.
The foregoing is only preferred embodiment of the present invention, all equalizations done according to the present patent application the scope of the claims change and modify, and all should belong to covering scope of the present invention.
Claims (7)
1. Android application program forever obtains a method for Root authority, it is characterized in that: comprise the steps:
Step 1, will the operation of using Root authority in Android application program, be needed to be write by C/C++ language, and be compiled into an Android system executable program file, and the function of described executable program file energy teaching display stand upgrade function and the communication with Android application program; Executable program file packing is integrated in Android application program;
Step 2, under Android system judgement/system/bin catalogue under whether there is described executable program file, no, then enter step 3; Be then judge that executable program file is the need of upgrading, upgrade, then Android application program is set up with this executable program file and is communicated, and calls self-upgrade function, carries out upgrading processing, and proceed to step 8 to this executable program file; Do not upgrade, then directly enter step 8;
The su program that step 3, Android application program run Android system carries out first time mandate to operation user;
Step 4, by Android system /system catalogue carries out weight carry for can write state;
Step 5, by Android system /authority of system/bin catalogue arranges, with ensure Android application program right/catalogue of system/bin has the authority write;
Step 6, described executable program file copied to described/system/bin catalogue under, and revise the owner of this executable program file authority classification and be affiliatedly grouped into Root;
Step 7, arrange the suid flag of executable program file, after arranging suid flag, namely executable program file just with possessory identity performed by Android application program, can have the operation of Root authority;
Step 8, Android application program perform executable program file and communicate with its foundation, as long as now Android application program needs the operation of using Root authority to be undertaken performing by executable program file, carry out repetitive endowment without the need to the su program by Android system.
2. Android application program according to claim 1 forever obtains the method for Root authority, it is characterized in that: the operation of described Root authority comprises: obtain file directory, mourn in silence installation procedure and Uninstaller.
3. Android application program according to claim 1 forever obtains the method for Root authority, it is characterized in that: described step 3 is specially: Android application program runs the su program of Android system, and obtain the output stream of su program, su order afterwards can directly be ordered toward output stream write and perform, now, toward the output stream write one arbitrary character Command of su program, the SuperUser of Android system can eject mandate dialog box, operation user clicks permission, then continue to perform described step 4, operation user clicks refusal, then process ends.
4. Android application program according to claim 1 forever obtains the method for Root authority, it is characterized in that: described step 4 is specially: toward output stream write first order of su program, by Android system /system catalogue carries out weight carry for can write state, this first order is: " mount – o remount – w – t [type] [device]/system ", wherein [type] is the file system type wanting carry, [device] is for wanting the equipment of carry, these two is /the relevant parameter of system catalogue carry, obtained by the shell-command of execution Android system.
5. Android application program according to claim 1 forever obtains the method for Root authority, it is characterized in that: described step 5 is specially: toward output stream write second order of su program, by Android system /authority of system/bin catalogue changes 777 into, with ensure Android application program right/catalogue of system/bin has the authority write, this second order is: " chmod 777/system/bin ".
6. Android application program according to claim 1 forever obtains the method for Root authority, it is characterized in that: described step 6 is specially: toward output stream write the 3rd order of su program, under executable program file being copied to the catalogue of described/system/bin, 3rd order is " dd if=[fromPath] of=[toPath] ", wherein [fromPath] is the path at executable program file now place, [toPath] path for copying to, the title of namely/system/bin/ executable program file; And toward output stream write the 4th order of su program, revise the owner of this executable program file authority classification and be affiliatedly grouped into root, the 4th order is " title of chown root:root/system/bin/ executable program file ".
7. Android application program according to claim 1 forever obtains the method for Root authority, it is characterized in that: described step 7 is specially: toward output stream write the 5th order of su program, the suid flag of executable program file is set, and be readable execution by executable program file priority assignation, namely executable program file priority assignation is 4755, wherein " 4 " are suid flags, namely executable program file just with possessory identity performed by Android application program, can have the operation of Root authority; 5th order is: " title of chmod 4755/system/bin/ executable program file ".
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210436649.9A CN102981835B (en) | 2012-11-02 | 2012-11-02 | Android application program permanent Root permission acquiring method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210436649.9A CN102981835B (en) | 2012-11-02 | 2012-11-02 | Android application program permanent Root permission acquiring method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102981835A CN102981835A (en) | 2013-03-20 |
| CN102981835B true CN102981835B (en) | 2015-06-10 |
Family
ID=47855900
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210436649.9A Active CN102981835B (en) | 2012-11-02 | 2012-11-02 | Android application program permanent Root permission acquiring method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102981835B (en) |
Families Citing this family (43)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103198265B (en) * | 2013-03-28 | 2017-12-05 | 上海斐讯数据通信技术有限公司 | A kind of method for opening mobile device root authority |
| CN103152366B (en) * | 2013-04-10 | 2015-12-23 | 魅族科技（中国）有限公司 | Obtain the method for terminal authorization, terminal and server |
| CN103324537A (en) * | 2013-05-17 | 2013-09-25 | Tcl集团股份有限公司 | Resource sharing method and device |
| CN103365685A (en) * | 2013-06-03 | 2013-10-23 | 深圳创维无线技术有限公司 | Super authority method and super authority device based on android |
| CN104252587B (en) * | 2013-06-25 | 2018-04-27 | 腾讯科技（深圳）有限公司 | Pull the method, apparatus and system of file |
| CN103324482A (en) * | 2013-06-27 | 2013-09-25 | 苏州创智宏云信息科技有限公司 | Android one-key root permission software |
| CN103473502A (en) * | 2013-09-16 | 2013-12-25 | 惠州Tcl移动通信有限公司 | Method and system for acquiring Root rights of android-based mobile terminal |
| CN103530534B (en) * | 2013-09-23 | 2016-06-29 | 北京理工大学 | A kind of Android program ROOT authorization method based on signature verification |
| CN104572158B (en) * | 2013-10-29 | 2019-01-04 | 腾讯科技（深圳）有限公司 | One kind running application program method and device with power user's identity |
| CN103559431A (en) * | 2013-11-11 | 2014-02-05 | 北京国双科技有限公司 | Detection method, device and system of Android system user permission |
| CN104636375B (en) | 2013-11-12 | 2019-05-07 | 中兴通讯股份有限公司 | A kind of automated back-up application data and the method and device restored on demand |
| CN103714287B (en) * | 2013-12-25 | 2015-07-01 | 北京奇虎科技有限公司 | Method and device for obtaining temporary Root authority |
| CN104809403A (en) * | 2014-01-24 | 2015-07-29 | 红板凳科技股份有限公司 | Root-preventing white screen method |
| CN103826215B (en) * | 2014-02-11 | 2018-03-02 | 北京奇虎科技有限公司 | A kind of method and apparatus for carrying out Root authority management on the terminal device |
| CN103888294B (en) * | 2014-02-28 | 2017-10-27 | 广州视睿电子科技有限公司 | Method and device for assigning router in Android system |
| CN104063303B (en) * | 2014-06-30 | 2019-07-16 | 上海斐讯数据通信技术有限公司 | A method of obtaining and discharge root authority |
| CN104134036B (en) * | 2014-07-26 | 2017-05-10 | 珠海市君天电子科技有限公司 | Method and device for obtaining Root permission |
| CN104217158A (en) * | 2014-09-17 | 2014-12-17 | 青岛海信移动通信技术股份有限公司 | Method for detecting system state of intelligent terminal and intelligent terminal |
| CN104199711B (en) * | 2014-09-29 | 2018-02-13 | 北京奇虎科技有限公司 | The method and apparatus for establishing root authority |
| CN104484611B (en) * | 2014-11-10 | 2018-12-21 | 福建联迪商用设备有限公司 | A kind of the subregion carry management-control method and device of android system |
| CN104348628A (en) * | 2014-12-01 | 2015-02-11 | 北京奇虎科技有限公司 | Method and device for obtaining local Root authority |
| CN104391729B (en) * | 2014-12-19 | 2018-05-01 | 北京奇虎科技有限公司 | Programme upgrade method and device based on Root authority |
| CN104506639A (en) * | 2014-12-29 | 2015-04-08 | 北京奇虎科技有限公司 | Root right acquiring method and device |
| CN108279855B (en) * | 2015-03-05 | 2021-07-06 | 青岛海信宽带多媒体技术有限公司 | Method for reading and writing storage device |
| CN106559546B (en) * | 2015-09-28 | 2020-09-04 | 腾讯科技（深圳）有限公司 | Method and device for controlling software to use network networking |
| CN105243325A (en) * | 2015-09-29 | 2016-01-13 | 北京奇虎科技有限公司 | Method for residual process file in mobile terminal, mobile terminal and server |
| CN105630544A (en) * | 2015-12-21 | 2016-06-01 | 小米科技有限责任公司 | System updating control method and apparatus as well as server device |
| CN106919812B (en) * | 2015-12-26 | 2020-06-16 | 腾讯科技（深圳）有限公司 | Application process authority management method and device |
| CN105956457B (en) * | 2016-04-27 | 2018-11-13 | 四川秘无痕信息安全技术有限责任公司 | A method of it frequently executing root authority and operates and obtain real-time results feedback |
| CN106529332B (en) * | 2016-10-25 | 2019-08-13 | Oppo广东移动通信有限公司 | A kind of authority control method of mobile terminal, device and mobile terminal |
| CN106650408B (en) * | 2016-12-09 | 2020-08-04 | 武汉斗鱼网络科技有限公司 | Method and system for judging whether android system has root permission |
| CN107068150A (en) * | 2017-05-03 | 2017-08-18 | 安利军 | A kind of Android intelligent sounds control method and system |
| CN109815726A (en) * | 2017-11-21 | 2019-05-28 | 中标软件有限公司 | The method and its background program building method of ordinary user's modification system file |
| CN108595214A (en) * | 2018-04-11 | 2018-09-28 | 北京海杭通讯科技有限公司 | Android user versions obtain the method and system of root privileges under SELinux compulsory modes |
| CN108920945B (en) * | 2018-05-02 | 2020-10-02 | 广州视源电子科技股份有限公司 | root authority obtaining and deleting method and device, terminal equipment and storage medium |
| CN109271781B (en) * | 2018-09-13 | 2020-11-17 | 西安交通大学 | Method and system for detecting super authority obtaining behavior of application program based on kernel |
| CN109815680B (en) * | 2018-12-27 | 2021-08-31 | 歌尔股份有限公司 | Application authority management method and device, terminal equipment and storage medium |
| CN110457894B (en) * | 2019-08-06 | 2021-08-03 | 惠州Tcl移动通信有限公司 | root authority distribution method and device, storage medium and terminal equipment |
| CN113254916A (en) * | 2021-05-25 | 2021-08-13 | 深圳市瑞驰信息技术有限公司 | Implementation method of root switch of android system |
| CN113688377B (en) * | 2021-07-27 | 2024-07-09 | 青岛中科英泰商用***股份有限公司 | Root authority management method and system of Android device |
| CN115499420A (en) * | 2022-09-14 | 2022-12-20 | 苏州龙信信息科技有限公司 | Data transmission method and device, electronic equipment and storage medium |
| CN116702163B (en) * | 2022-09-27 | 2024-06-21 | 荣耀终端有限公司 | Authority management method and terminal equipment |
| CN115391794A (en) * | 2022-10-27 | 2022-11-25 | 中孚安全技术有限公司 | Method, system and equipment for adding permission in application program starting process |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030028508A1 (en) * | 2001-08-06 | 2003-02-06 | Joseph Quinlan | Method and apparatus for controlling the performance of a file system mount operation by a user lacking superuser authority |
| CN102289633A (en) * | 2011-09-02 | 2011-12-21 | 广东欧珀移动通信有限公司 | Method for managing dynamic permission of application program under Android platform |
-
2012
- 2012-11-02 CN CN201210436649.9A patent/CN102981835B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030028508A1 (en) * | 2001-08-06 | 2003-02-06 | Joseph Quinlan | Method and apparatus for controlling the performance of a file system mount operation by a user lacking superuser authority |
| CN102289633A (en) * | 2011-09-02 | 2011-12-21 | 广东欧珀移动通信有限公司 | Method for managing dynamic permission of application program under Android platform |
Non-Patent Citations (3)
| Title |
|---|
| AIY_YA.HTTP://BLOG.SINA.COM.ZH/S/BLOG_9659CD4201018UJX.HTML.《ANDROID ROOT权限获取原理详解》.2012, * |
| COLIN.HTTP://WWW.360DOC.COM/CONTENT/11/1220/00/4165_173524951.SHTML.《ANDROID ROOT权限破解原理分析》.2011, * |
| 浅析Android平台ROOT权限;姜颖韬;《科技经济市场》;20111031(第10期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102981835A (en) | 2013-03-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102981835B (en) | Android application program permanent Root permission acquiring method | |
| US9075955B2 (en) | Managing permission settings applied to applications | |
| CN103544447B (en) | A kind of method preventing confidential information from revealing based on Android system and terminal | |
| DE112012001389T5 (en) | Secure execution of an unsecured app on a device | |
| CN109829286B (en) | User authority management system and method for WEB application | |
| CN103905651A (en) | Method and system for application permission management in intelligent terminal | |
| CN104156660B (en) | A kind of Android authority fine-grained access control method based on running environment state | |
| CN103870306A (en) | Method and device for installing application program on basis of intelligent terminal equipment | |
| CN105046146A (en) | Resource access method of Android system | |
| US11743295B2 (en) | Methods and apparatus to provide resource security | |
| CN104267982A (en) | Application program start control system and method | |
| Elkhodary et al. | A survey of approaches to adaptive application security | |
| CN103455520A (en) | Method and device for accessing Android database | |
| CN106169042A (en) | The method and device of administration authority | |
| CN105205413A (en) | Data protecting method and device | |
| JP2004158007A (en) | Computer access authorization | |
| CN105373714B (en) | A kind of user authority control method and device | |
| CN104281803A (en) | System permission management method and equipment | |
| CA2830880C (en) | Managing permission settings applied to applications | |
| CN111651738A (en) | Fine-grained role authority unified management method based on front-end and back-end separation framework and electronic device | |
| CN103763370B (en) | A kind of method, system and device for changing mobile terminal workspace screen-lock password | |
| CN105868639A (en) | Kernel vulnerability repair method and device | |
| CN103906045B (en) | A kind of monitoring method and system of mobile terminal privacy taking and carring away | |
| CN105786551A (en) | Application program operation access control method and system | |
| CN103885784A (en) | Method for establishing Android platform with security module and plugging function |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| C41 | Transfer of patent application or patent right or utility model | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20160106 Address after: 100000, No. two, building 17, Zhongguancun Software Park, 8 northeast Wang Xi Road, Beijing, Haidian District, A2 Patentee after: BAIDU.COM TIMES TECHNOLOGY (BEIJING) Co.,Ltd. Address before: 350000, 403A building, four floor, Torch Innovation Building, 8 star road, Fuzhou Development Zone, Fuzhou, Fujian, China Patentee before: Fuzhou Boyuan Wireless Network Technology Co., Ltd. |