CN112799739A - Application protection method and terminal - Google Patents
Application protection method and terminal Download PDFInfo
- Publication number
- CN112799739A CN112799739A CN202110154141.9A CN202110154141A CN112799739A CN 112799739 A CN112799739 A CN 112799739A CN 202110154141 A CN202110154141 A CN 202110154141A CN 112799739 A CN112799739 A CN 112799739A
- Authority
- CN
- China
- Prior art keywords
- application
- judging whether
- protection
- protection file
- exists
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44594—Unloading
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
Abstract
The invention discloses an application protection method and a terminal, which judge whether an identity label of a sending terminal is a root authority or not by receiving an application unloading request sent by the sending terminal, if so, the application is allowed to be unloaded, if not, whether equipment corresponding to the application is in a use state or not is judged, if not, an unloading protection process is executed, if not, the application is allowed to be unloaded, the root authority represents the highest authority, the sending terminal with the identity label as the root authority allows the application to be unloaded, when the identity label of the sending terminal is not the root authority and the equipment corresponding to the application is in a non-use state, a developer is convenient to carry out system development and does not enter the unloading protection process, when the equipment is in the use state, the description is that a common user carries out unloading operation through the sending terminal, executes the unloading protection process, and can protect the unloaded application according to requirements, and the protection appeal of various users to the specified application is met.
Description
Technical Field
The invention relates to the technical field of electronics, in particular to an application protection method and a terminal.
Background
With the continuous development of the Android system, the Android system is used for more and more devices, such as a POS machine, a cash register and the like.
The mobile phone end manufacturer does not need to make different versions for the application pre-installed by the customer according to different customers, and the requirement of unloading protection on the application by a specific user is less met. However, due to the industry nature of devices such as POS and cash registers, many customers such as banks, acquiring agencies and merchants have a great need for deep protection of their designated applications when they are uninstalled.
At present, some manufacturers preset the applications that cannot be uninstalled as specified by a customer as system applications, and some manufacturers specify some applications that cannot be uninstalled to a user when the manufacturers leave a factory, but the requirements of multiple users for flexibly uninstalling and protecting the applications of the same system version cannot be realized.
Disclosure of Invention
The technical problem to be solved by the invention is as follows: an application protection method and a terminal are provided, which can protect the uninstalled application according to the requirement.
In order to solve the technical problems, the invention adopts a technical scheme that:
an application protection method comprising the steps of:
receiving an application unloading request sent by a sending terminal;
and judging whether the identity of the sending terminal is the root authority, if so, allowing the application to be uninstalled, otherwise, judging whether the equipment corresponding to the application is in a use state, if so, executing an uninstalling protection process, and if not, allowing the application to be uninstalled.
In order to solve the technical problem, the invention adopts another technical scheme as follows:
an application protection terminal comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program:
receiving an application unloading request sent by a sending terminal;
and judging whether the identity of the sending terminal is the root authority, if so, allowing the application to be uninstalled, otherwise, judging whether the equipment corresponding to the application is in a use state, if so, executing an uninstalling protection process, and if not, allowing the application to be uninstalled.
The invention has the beneficial effects that:
judging whether the identity of the sending terminal is the root authority or not by receiving an application uninstalling request sent by the sending terminal, if so, the application is allowed to be unloaded, if not, whether the equipment corresponding to the application is in a use state is judged, if yes, executing the unloading protection process, if not, allowing to unload the application, the root authority represents the highest authority, the sending terminal with the identity mark as the root authority allows to unload the application, when the identity of the sending terminal is not the root authority and the device corresponding to the application is in the non-use state, in order to facilitate the system development of a developer, the uninstallation protection process is not entered, when the device is in a use state, the description is that the common user carries out the unloading operation through the sending terminal, executes the unloading protection process, can protect the unloaded application according to the requirement, and meets the protection requirements of various users on the specified application.
Drawings
FIG. 1 is a flowchart illustrating steps of a method for application protection according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of an application protection terminal according to an embodiment of the present invention;
fig. 3 is a flowchart of an application protection method according to an embodiment of the present invention.
Detailed Description
In order to explain technical contents, achieved objects, and effects of the present invention in detail, the following description is made with reference to the accompanying drawings in combination with the embodiments.
Referring to fig. 1, an embodiment of the present invention provides an application protection method, including:
receiving an application unloading request sent by a sending terminal;
and judging whether the identity of the sending terminal is the root authority, if so, allowing the application to be uninstalled, otherwise, judging whether the equipment corresponding to the application is in a use state, if so, executing an uninstalling protection process, and if not, allowing the application to be uninstalled.
From the above description, the beneficial effects of the present invention are: judging whether the identity of the sending terminal is the root authority or not by receiving an application uninstalling request sent by the sending terminal, if so, the application is allowed to be unloaded, if not, whether the equipment corresponding to the application is in a use state is judged, if yes, executing the unloading protection process, if not, allowing to unload the application, the root authority represents the highest authority, the sending terminal with the identity mark as the root authority allows to unload the application, when the identity of the sending terminal is not the root authority and the device corresponding to the application is in the non-use state, in order to facilitate the system development of a developer, the uninstallation protection process is not entered, when the device is in a use state, the description is that the common user carries out the unloading operation through the sending terminal, executes the unloading protection process, can protect the unloaded application according to the requirement, and meets the protection requirements of various users on the specified application.
Further, the executing the uninstall protection process includes:
inquiring the application according to a preset application protection file, wherein the preset application protection file comprises a first application protection file and a second application protection file;
and judging whether the application exists in the first application protection file, if so, forbidding to unload the application, if not, judging whether third-party verification is started, if so, executing the third-party verification, if not, judging whether the application exists in the second application protection file, if so, forbidding to unload the application, and if not, allowing to unload the application.
According to the description, the preset application protection file comprises the first application protection file and the second application protection file, the application is inquired according to the preset application protection file, the applications which need to be protected by a manufacturer and a user are stored in the preset application protection file, whether the unloaded application is the application which needs to be protected and is appointed by the manufacturer and the client or not can be determined, and therefore the unloaded application is protected according to the requirements of the manufacturer and the client.
Further, the determining whether the application exists in the first application protection file includes:
matching the application package name of the application with the application package name containing wildcards in the first application protection file;
judging whether the application exists in the first application protection file or not according to a matching result;
the determining whether the application exists in the second application protection file includes:
matching the application package name of the application with the application package name containing wildcards in the second application protection file;
and judging whether the application exists in the second application protection file or not according to the matching result.
According to the description, the application package name in the preset application protection file can support the wildcard character, and when the first application protection file and the second application protection file are judged to exist in the application, the application package name of the application is matched with the application package name containing the wildcard character in the preset application protection file, so that the application package names of multiple versions in the preset application protection file can be processed at one time, and the query efficiency is improved.
Further, the performing the third party verification includes:
and judging whether the APK verified by the third party is legal or not, if not, executing the step of judging whether the application exists in the second application protection file, if so, judging whether the verification of binding the third party is successful or not, if not, executing the step of judging whether the application exists in the second application protection file or not, and if so, verifying the application through the third party.
Further, the method also comprises the following steps:
storing a preset key corresponding to the application which is forbidden to be uninstalled to the third party for verification;
the verifying the application through the third party verification comprises:
and judging whether a preset secret key corresponding to the application exists in the third-party verification, if so, forbidding to uninstall the application, and if not, allowing to uninstall the application.
As can be seen from the above description, for an application that is not included in the first application protection file and is already checked by the third party, the third party check is performed, and the specific user can determine the application that needs to be protected in the third party check, thereby implementing the deep protection of the specific user on the specific application.
Referring to fig. 2, another embodiment of the present invention provides an application protection terminal, including a memory, a processor, and a computer program stored in the memory and running on the processor, where the processor executes the computer program to implement the following steps:
receiving an application unloading request sent by a sending terminal;
and judging whether the identity of the sending terminal is the root authority, if so, allowing the application to be uninstalled, otherwise, judging whether the equipment corresponding to the application is in a use state, if so, executing an uninstalling protection process, and if not, allowing the application to be uninstalled.
From the above description, the beneficial effects of the present invention are: judging whether the identity of the sending terminal is the root authority or not by receiving an application uninstalling request sent by the sending terminal, if so, the application is allowed to be unloaded, if not, whether the equipment corresponding to the application is in a use state is judged, if yes, executing the unloading protection process, if not, allowing to unload the application, the root authority represents the highest authority, the sending terminal with the identity mark as the root authority allows to unload the application, when the identity of the sending terminal is not the root authority and the device corresponding to the application is in the non-use state, in order to facilitate the system development of a developer, the uninstallation protection process is not entered, when the device is in a use state, the description is that the common user carries out the unloading operation through the sending terminal, executes the unloading protection process, can protect the unloaded application according to the requirement, and meets the protection requirements of various users on the specified application.
Further, the executing the uninstall protection process includes:
inquiring the application according to a preset application protection file, wherein the preset application protection file comprises a first application protection file and a second application protection file;
and judging whether the application exists in the first application protection file, if so, forbidding to unload the application, if not, judging whether third-party verification is started, if so, executing the third-party verification, if not, judging whether the application exists in the second application protection file, if so, forbidding to unload the application, and if not, allowing to unload the application.
According to the description, the preset application protection file comprises the first application protection file and the second application protection file, the application is inquired according to the preset application protection file, the applications which need to be protected by a manufacturer and a user are stored in the preset application protection file, whether the unloaded application is the application which needs to be protected and is appointed by the manufacturer and the client or not can be determined, and therefore the unloaded application is protected according to the requirements of the manufacturer and the client.
Further, the determining whether the application exists in the first application protection file includes:
matching the application package name of the application with the application package name containing wildcards in the first application protection file;
judging whether the application exists in the first application protection file or not according to a matching result;
the determining whether the application exists in the second application protection file includes:
matching the application package name of the application with the application package name containing wildcards in the second application protection file;
and judging whether the application exists in the second application protection file or not according to the matching result.
According to the description, the application package name in the preset application protection file can support the wildcard character, and when the first application protection file and the second application protection file are judged to exist in the application, the application package name of the application is matched with the application package name containing the wildcard character in the preset application protection file, so that the application package names of multiple versions in the preset application protection file can be processed at one time, and the query efficiency is improved.
Further, the performing the third party verification includes:
and judging whether the APK verified by the third party is legal or not, if not, executing the step of judging whether the application exists in the second application protection file, if so, judging whether the verification of binding the third party is successful or not, if not, executing the step of judging whether the application exists in the second application protection file or not, and if so, verifying the application through the third party.
Further, the method also comprises the following steps:
storing a preset key corresponding to the application which is forbidden to be uninstalled to the third party for verification;
the verifying the application through the third party verification comprises:
and judging whether a preset secret key corresponding to the application exists in the third-party verification, if so, forbidding to uninstall the application, and if not, allowing to uninstall the application.
As can be seen from the above description, for an application that is not included in the first application protection file and is already checked by the third party, the third party check is performed, and the specific user can determine the application that needs to be protected in the third party check, thereby implementing the deep protection of the specific user on the specific application.
The application protection method and the terminal can be applied to relevant equipment using an Android system, and are described in the following by specific embodiments:
example one
Referring to fig. 1 and 3, an application protection method of the present embodiment includes the steps of:
s1, receiving an application uninstalling request sent by a sending terminal;
for example, a PMS (Package Manager Service) receives an application offload request sent by an offload initiator;
s2, judging whether the identity of the sending terminal is a root authority, if so, allowing the application to be uninstalled, if not, judging whether the equipment corresponding to the application is in a use state, if so, executing an uninstalling protection process, and if not, allowing the application to be uninstalled;
the state of the equipment comprises a debugging state and a using state, and the equipment is convenient for a developer to develop when in the debugging state and does not trigger an unloading protection process;
for example, as shown in fig. 3, it is determined whether a UID (User Identification) of the offload initiator is Root authority, if so, the application is allowed to be offloaded, if not, it is determined whether a device corresponding to the application is in a use state, if so, an offload protection process is executed, and if not, the application is allowed to be offloaded.
Example two
Referring to fig. 3, the present embodiment further defines how to execute the offload protection process based on the first embodiment, and specifically includes:
inquiring the application according to a preset application protection file, wherein the preset application protection file comprises a first application protection file and a second application protection file;
the preset application protection file comprises a manufacturer application protection file and a client application protection file, and the priority of the manufacturer application protection file is higher than that of the client application protection file;
for example, when querying whether the application exists in a preset application protection file, querying in a manufacturer application protection file and then querying in a client application protection file;
in this embodiment, the first application protection file is a manufacturer application protection file, and the second application protection file is a client application protection file;
judging whether the application exists in the first application protection file or not, if so, forbidding to unload the application, if not, judging whether third-party verification is started or not, if so, executing the third-party verification, if not, judging whether the application exists in the second application protection file or not, if so, forbidding to unload the application, and if not, allowing to unload the application;
specifically, the determining whether the application exists in the first application protection file includes:
matching the application package name of the application with the application package name containing wildcards in the first application protection file;
judging whether the application exists in the first application protection file or not according to a matching result;
the determining whether the application exists in the second application protection file includes:
matching the application package name of the application with the application package name containing wildcards in the second application protection file;
judging whether the application exists in the second application protection file or not according to a matching result;
for example, as shown in fig. 3, the application is queried according to a preset application protection file, the application package name of the application is matched with the application package name containing a wildcard in a vendor application protection file, whether the application exists in the vendor application protection file is determined according to a matching result, if the application exists in the vendor application protection file, the application is prohibited from being uninstalled, if the application does not exist in the vendor application protection file, whether third-party verification is started is determined, if yes, third-party verification is executed, if not, the application package name of the application is matched with the application package name containing a wildcard in a client application protection file, whether the application exists in the client application protection file is determined according to a matching result, if yes, the application is prohibited from being uninstalled, and if not, the application is permitted to be uninstalled;
the client application protection file can be installed to a designated position of a sending terminal in the form of pkg files (installation package configuration files), in order to guarantee the validity and the security of the file, the client application protection file needs to be signed, and the validity of the file signature is verified when the PMS is initialized.
EXAMPLE III
Referring to fig. 3, the embodiment further defines how to perform the third party verification based on the first and second embodiments, and specifically includes:
storing a preset key corresponding to the application which is forbidden to be uninstalled to the third party for verification;
the preset key is provided by a system and is generated by an RSA private key, an encryption application package name, signature information and the like, and the preset key is required to be filled in the corresponding < meta-data > for verification by a third party;
judging whether the APK verified by the third party is legal or not, if not, executing and judging whether the application step exists in the second application protection file or not, if so, judging whether the verification of binding the third party is successful or not, if not, executing and judging whether the application step exists in the second application protection file or not, and if so, verifying and verifying the application through the third party;
the PMS calls an authentication Interface provided for the verification of the third party of the protected application through an Android Interface Definition Language (AIDL);
specifically, the verifying the application through the third party verification includes:
judging whether a preset secret key corresponding to the application exists in the third-party verification, if so, forbidding to uninstall the application, and if not, allowing to uninstall the application;
for example, as shown in fig. 3, it is determined whether the APK verified by the third party is legal, if not, a step of matching the application package name of the application with the application package name including the wildcard in the client application protection file is performed, if so, it is determined whether the verification by the third party is successful, if not, a step of matching the application package name of the application with the application package name including the wildcard in the client application protection file is performed, and if so, the application is verified by the third party;
and judging whether a preset key corresponding to the application exists in the third-party verification, if so, forbidding to uninstall the application, and if not, allowing to uninstall the application.
Example four
Referring to fig. 2, an application protection terminal includes a memory, a processor, and a computer program stored in the memory and capable of running on the processor, and when the processor executes the computer program, the steps in the first embodiment, the second embodiment, or the third embodiment are implemented.
In summary, according to the application protection method and the terminal provided by the present invention, by receiving an application uninstalling request sent by a sending terminal, it is determined whether an identity of the sending terminal is a root authority, if so, the application is allowed to be uninstalled, if not, it is determined whether a device corresponding to the application is in a use state, if so, an uninstall protection process is executed, and if not, the application is allowed to be uninstalled; the unloading protection executing process is specifically that the application is inquired according to a preset application protection file, the preset application protection file comprises a first application protection file and a second application protection file, whether the application exists in the first application protection file is judged, if the application exists in the first application protection file, unloading of the application is forbidden, if the application does not exist in the first application protection file, whether third-party verification is started is judged, if yes, the third-party verification is executed, if no, whether the application exists in the second application protection file is judged, if yes, the application is forbidden to be unloaded, if not, the application is allowed to be unloaded, and whether the unloaded application is the application which needs to be protected and is specified by a manufacturer and a customer can be determined; the third-party verification is carried out on the applications which are not contained in the first application protection file and are opened by the third-party verification, and a specific user can determine the applications needing to be protected in the third-party verification, so that the deep protection of the specific user on the specific applications is realized; when the identity of the sending terminal is not the root authority and the device corresponding to the application is in the non-use state, the unloading protection process is not performed for a developer to conveniently develop the system, and when the device is in the use state, the unloading operation is performed by a common user through the sending terminal to execute the unloading protection process, and the unloaded application can be protected according to the requirement, so that the protection appeal of various users to the specified application is met.
The above description is only an embodiment of the present invention, and not intended to limit the scope of the present invention, and all equivalent changes made by using the contents of the present specification and the drawings, or applied directly or indirectly to the related technical fields, are included in the scope of the present invention.
Claims (10)
1. An application protection method, comprising the steps of:
receiving an application unloading request sent by a sending terminal;
and judging whether the identity of the sending terminal is the root authority, if so, allowing the application to be uninstalled, otherwise, judging whether the equipment corresponding to the application is in a use state, if so, executing an uninstalling protection process, and if not, allowing the application to be uninstalled.
2. The application protection method according to claim 1, wherein the executing the offload protection process comprises:
inquiring the application according to a preset application protection file, wherein the preset application protection file comprises a first application protection file and a second application protection file;
and judging whether the application exists in the first application protection file, if so, forbidding to unload the application, if not, judging whether third-party verification is started, if so, executing the third-party verification, if not, judging whether the application exists in the second application protection file, if so, forbidding to unload the application, and if not, allowing to unload the application.
3. The method according to claim 2, wherein the determining whether the application exists in the first application protection file comprises:
matching the application package name of the application with the application package name containing wildcards in the first application protection file;
judging whether the application exists in the first application protection file or not according to a matching result;
the determining whether the application exists in the second application protection file includes:
matching the application package name of the application with the application package name containing wildcards in the second application protection file;
and judging whether the application exists in the second application protection file or not according to the matching result.
4. The application protection method of claim 2, wherein the performing the third-party verification comprises:
and judging whether the APK verified by the third party is legal or not, if not, executing the step of judging whether the application exists in the second application protection file, if so, judging whether the verification of binding the third party is successful or not, if not, executing the step of judging whether the application exists in the second application protection file or not, and if so, verifying the application through the third party.
5. The application protection method according to claim 4, further comprising the steps of:
storing a preset key corresponding to the application which is forbidden to be uninstalled to the third party for verification;
the verifying the application through the third party verification comprises:
and judging whether a preset secret key corresponding to the application exists in the third-party verification, if so, forbidding to uninstall the application, and if not, allowing to uninstall the application.
6. An application protection terminal comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the following steps when executing the computer program:
receiving an application unloading request sent by a sending terminal;
and judging whether the identity of the sending terminal is the root authority, if so, allowing the application to be uninstalled, otherwise, judging whether the equipment corresponding to the application is in a use state, if so, executing an uninstalling protection process, and if not, allowing the application to be uninstalled.
7. The application protection terminal according to claim 6, wherein the executing the offload protection process comprises:
inquiring the application according to a preset application protection file, wherein the preset application protection file comprises a first application protection file and a second application protection file;
and judging whether the application exists in the first application protection file, if so, forbidding to unload the application, if not, judging whether third-party verification is started, if so, executing the third-party verification, if not, judging whether the application exists in the second application protection file, if so, forbidding to unload the application, and if not, allowing to unload the application.
8. The application protection terminal of claim 7, wherein the determining whether the application exists in the first application protection file comprises:
matching the application package name of the application with the application package name containing wildcards in the first application protection file;
judging whether the application exists in the first application protection file or not according to a matching result;
the determining whether the application exists in the second application protection file includes:
matching the application package name of the application with the application package name containing wildcards in the second application protection file;
and judging whether the application exists in the second application protection file or not according to the matching result.
9. The application protection terminal of claim 7, wherein the performing the third party verification comprises:
and judging whether the APK verified by the third party is legal or not, if not, executing the step of judging whether the application exists in the second application protection file, if so, judging whether the verification of binding the third party is successful or not, if not, executing the step of judging whether the application exists in the second application protection file or not, and if so, verifying the application through the third party.
10. The application protection terminal according to claim 9, further comprising the steps of:
storing a preset key corresponding to the application which is forbidden to be uninstalled to the third party for verification;
the verifying the application through the third party verification comprises:
and judging whether a preset secret key corresponding to the application exists in the third-party verification, if so, forbidding to uninstall the application, and if not, allowing to uninstall the application.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110154141.9A CN112799739A (en) | 2021-02-04 | 2021-02-04 | Application protection method and terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110154141.9A CN112799739A (en) | 2021-02-04 | 2021-02-04 | Application protection method and terminal |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112799739A true CN112799739A (en) | 2021-05-14 |
Family
ID=75814238
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110154141.9A Pending CN112799739A (en) | 2021-02-04 | 2021-02-04 | Application protection method and terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112799739A (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100077475A1 (en) * | 2008-09-22 | 2010-03-25 | Microsoft Corporation | Partial installation based on available privileges |
| CN101727358A (en) * | 2009-12-15 | 2010-06-09 | 中国电信股份有限公司 | Method and system for realizing inter-Widget-application communication |
| KR101308859B1 (en) * | 2012-02-24 | 2013-09-16 | 주식회사 팬택 | Terminal having temporary root authority granting function and root authority granting method using the same |
| CN103595774A (en) * | 2013-11-01 | 2014-02-19 | 北京奇虎科技有限公司 | System application uninstalling method and device with terminal based on server side |
| CN104023032A (en) * | 2014-06-23 | 2014-09-03 | 北京握奇智能科技有限公司 | Application limited unloading method based on dependable execution environment technology, server and terminal |
| CN104461656A (en) * | 2014-12-26 | 2015-03-25 | 深圳数字电视国家工程实验室股份有限公司 | Application program unloading protection method and system based on Android platform |
| US20190196801A1 (en) * | 2017-12-22 | 2019-06-27 | Toshiba Tec Kabushiki Kaisha | Method and apparatus for application development environment |
-
2021
- 2021-02-04 CN CN202110154141.9A patent/CN112799739A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100077475A1 (en) * | 2008-09-22 | 2010-03-25 | Microsoft Corporation | Partial installation based on available privileges |
| CN101727358A (en) * | 2009-12-15 | 2010-06-09 | 中国电信股份有限公司 | Method and system for realizing inter-Widget-application communication |
| KR101308859B1 (en) * | 2012-02-24 | 2013-09-16 | 주식회사 팬택 | Terminal having temporary root authority granting function and root authority granting method using the same |
| CN103595774A (en) * | 2013-11-01 | 2014-02-19 | 北京奇虎科技有限公司 | System application uninstalling method and device with terminal based on server side |
| CN104023032A (en) * | 2014-06-23 | 2014-09-03 | 北京握奇智能科技有限公司 | Application limited unloading method based on dependable execution environment technology, server and terminal |
| CN104461656A (en) * | 2014-12-26 | 2015-03-25 | 深圳数字电视国家工程实验室股份有限公司 | Application program unloading protection method and system based on Android platform |
| US20190196801A1 (en) * | 2017-12-22 | 2019-06-27 | Toshiba Tec Kabushiki Kaisha | Method and apparatus for application development environment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8479005B2 (en) | Applet, archive file generation method, archive file generation program, and archive file generation device | |
| JP4440983B2 (en) | Secure application distribution and execution in a wireless environment | |
| US8086861B2 (en) | Information processing terminal and status notification method | |
| US20100229242A1 (en) | Program execution control system, program execution control method and computer program for program execution control | |
| US20080104416A1 (en) | Apparatus and method for enabling applications on a security processor | |
| CN108763951B (en) | Data protection method and device | |
| JP2005182789A (en) | Method and system for ensuring that software update may be installed or run only on specific device or class of devices | |
| CN108780482B (en) | Method and device for managing applications in a secure device | |
| US11425127B2 (en) | Securing application behavior in serverless computing | |
| CN109344605B (en) | Authority control method and system of intelligent POS machine | |
| CN108595950A (en) | A kind of safe Enhancement Methods of SGX of combination remote authentication | |
| CN106548065B (en) | Application program installation detection method and device | |
| CN109460653B (en) | Rule engine based verification method, verification device, storage medium and apparatus | |
| CN112231702A (en) | Application protection method, device, equipment and medium | |
| JP4526383B2 (en) | Tamper evident removable media for storing executable code | |
| CN112134905B (en) | Android system based signature method, device and equipment | |
| CN114329358A (en) | Application signature method and system, transaction terminal and service platform | |
| CN109902500B (en) | Method and system for realizing service call data security through link library | |
| CN112799739A (en) | Application protection method and terminal | |
| CN107315610B (en) | Method, device and computer readable storage medium for realizing password function | |
| CN110602051A (en) | Information processing method based on consensus protocol and related device | |
| CN106648770B (en) | Generation method, loading method and device of application program installation package | |
| CN113220314B (en) | APP resource loading and APK generation method, device, equipment and medium | |
| CN112364340B (en) | Authority management method, device, equipment and computer readable storage medium | |
| CN111695113B (en) | Terminal software installation compliance detection method and device and computer equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210514 |
|
| RJ01 | Rejection of invention patent application after publication |