CN106529218B - Application verification method and device - Google Patents
Application verification method and device Download PDFInfo
- Publication number
- CN106529218B CN106529218B CN201610971662.2A CN201610971662A CN106529218B CN 106529218 B CN106529218 B CN 106529218B CN 201610971662 A CN201610971662 A CN 201610971662A CN 106529218 B CN106529218 B CN 106529218B
- Authority
- CN
- China
- Prior art keywords
- application
- feature code
- unique feature
- signature
- fingerprint
- 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
- 238000012795 verification Methods 0.000 title claims abstract description 44
- 238000000034 method Methods 0.000 title claims abstract description 33
- 230000004044 response Effects 0.000 claims abstract description 28
- 238000009434 installation Methods 0.000 claims description 9
- 238000012545 processing Methods 0.000 claims description 8
- 230000006870 function Effects 0.000 description 27
- 238000010586 diagram Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 230000007246 mechanism Effects 0.000 description 3
- 230000003068 static effect Effects 0.000 description 2
- 101100217298 Mus musculus Aspm gene Proteins 0.000 description 1
- 241000700605 Viruses Species 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- ZXQYGBMAQZUVMI-GCMPRSNUSA-N gamma-cyhalothrin Chemical compound CC1(C)[C@@H](\C=C(/Cl)C(F)(F)F)[C@H]1C(=O)O[C@H](C#N)C1=CC=CC(OC=2C=CC=CC=2)=C1 ZXQYGBMAQZUVMI-GCMPRSNUSA-N 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- 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/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
- G06F21/12—Protecting executable software
- G06F21/121—Restricting unauthorised execution of programs
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2463/00—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00
- H04L2463/101—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00 applying security measures for digital rights management
Abstract
The application provides an application verification method and device, wherein the application integrates a component, and the method is applied to the component and comprises the following steps: when the component is called by the application, sending a unique feature code acquisition request to a server; receiving a response returned by the server; if the response carries the unique feature code of the application, acquiring the unique feature code of the application from the application; and checking whether the unique feature code acquired from the application is consistent with the unique feature code returned by the server side, if so, confirming that the application passes the verification, and otherwise, confirming that the application does not pass the verification. The method can effectively prevent the components from being illegally used by counterfeit applications, and the method does not need to modify the codes of the components and the applications too much, and has high flexibility and strong operability.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to an application verification method and apparatus.
Background
The components may be used to implement certain functionality of the software product, such as may implement push technology, image recognition technology, mobile payment technology, and so on. The developer can directly call the functions of the components by selecting the proper components to be integrated in the application, and the development of each function of the application is not needed.
Charging is currently implemented for a portion of the components. In order to secure the benefit of the client and the client, the charging component needs to have the authority to identify whether each application has the right to use the component.
One method is to write a signature of an authorized application in advance in a code of a component, and when an application integrated with the component requests to use a function of the component, the component acquires the signature of the application and compares the signature with a signature written in advance in the code of the component, thereby determining whether the application has an authority.
However, this approach lacks flexibility, and the component needs to modify its own code for each authorized application, and is therefore not very operational.
Disclosure of Invention
In view of this, the present application provides an application checking method and apparatus, which can effectively prevent an assembly from being illegally used, and does not need to modify too many codes of the assembly and the application itself, and has high flexibility and strong operability.
Specifically, the method is realized through the following technical scheme:
in a first aspect of the present application, there is provided an application verification method, where the application integrates a component, and the method is applied to the component, and includes:
when the component is called by the application, sending a unique feature code acquisition request to a server;
receiving a response returned by the server;
if the response carries a unique signature of the application, then
Acquiring a unique feature code of the application from the application;
and checking whether the unique feature code acquired from the application is consistent with the unique feature code returned by the server side, if so, confirming that the application passes the verification, and otherwise, confirming that the application does not pass the verification.
In a second aspect of the present application, an application verification apparatus is provided, which has a function of implementing the above method. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules or units corresponding to the above functions.
In one possible implementation, the apparatus includes:
the sending unit is used for sending a unique feature code acquisition request to a server when a component integrated in an application is called by the application request;
the receiving unit is used for receiving a response returned by the server;
the processing unit is used for acquiring the unique feature code of the application from the application if the response carries the unique feature code of the application; and checking whether the unique feature code acquired from the application is consistent with the unique feature code returned by the server side, if so, confirming that the application passes the verification, and otherwise, confirming that the application does not pass the verification.
In another possible implementation manner, the apparatus includes a processor, a transceiver, and a memory for storing instructions executable by the processor, wherein the processor, the transceiver, and the memory are connected to each other through a bus; the processor is configured to perform the following operations:
when a component integrated in an application is called by the application, a unique feature code acquisition request is sent to a server through the transceiver;
receiving a response returned by the server through the transceiver;
if the response carries a unique signature of the application, then
Acquiring a unique feature code of the application from the application;
and checking whether the unique feature code acquired from the application is consistent with the unique feature code returned by the server side, if so, confirming that the application passes the verification, and otherwise, confirming that the application does not pass the verification.
According to the technical scheme, the true unique feature code of the application is stored in the server, when the application on the terminal is started, the application integrated component interacts with the server, so that the true unique feature code of the application is obtained, whether the application is a counterfeit application is identified by comparing whether the true unique feature code is consistent with the unique feature code obtained from the application, and therefore the component can be effectively prevented from being illegally used by the counterfeit application.
Drawings
Fig. 1 is a flowchart of an application verification method provided in an embodiment of the present application;
fig. 2 is a functional block diagram of an application verification apparatus according to an embodiment of the present disclosure;
fig. 3 is a hardware architecture diagram of another application verification apparatus according to an embodiment of the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
Hereinafter, some terms in the present application will be explained.
The component described in the present application refers to a software function module that performs a specific function, and the component can be loaded and called by application software in a static or dynamic manner, or can be integrated with the application software and called by the application software through a public interface. One release form of the component may be a Software Development Kit (SDK), where the SDK is a Software Development Kit (SDK) generally provided by a third-party service provider for implementing a function of a Software product, and an application developer may purchase the SDK, include the SDK in its own application Software project, integrate the function of the component into its own application by calling an application program interface API in the SDK, and finally compile and connect the SDK into an executable program. Another release form of the described component may be a form that can be dynamically loaded by the application software, for example, a form of a dynamic link library, and this form of component may be integrated with the application software by means of mobile application packaging (APP Wrapping) or the like, and is loaded and called by the application in a static or dynamic form through an interface disclosed by the component.
The module described in the application has a function of verifying the authenticity of the application, and the verification function inside the module can be automatically triggered when the module is called.
A "digital certificate" is a file containing public key owner information and a public key that is digitally signed by a certificate authority. Digital certificates generally contain the following: the issuing authority (Issuer) of the certificate, the Validity period (Validity) of the certificate, the public key of the sender of the message, the owner (Subject) of the certificate, the algorithm used for digital signature, etc.
A "unique signature" is a signature that uniquely identifies an application, and by means of the unique signature, it is possible to identify whether the application has been tampered with. Specifically, the unique feature code may be a public key, a signature, a digital certificate, or an executable file of the application, or may be a public key fingerprint, a signature fingerprint, a digital certificate fingerprint, or an executable file fingerprint of the application. For example, on the IOS operating system, the determination of application uniqueness may be made by a Mach object (Mach-O) type executable file. The fingerprint is a ciphertext obtained by encrypting information such as a public key, a signature, a digital certificate, an executable file and the like by using a fingerprint algorithm in order to ensure that the information is not tampered.
The fingerprint Algorithm mentioned here may be "MD 5(Message Digest Algorithm, fifth edition)" or "SHA (Secure Hash Algorithm)", or other encryption algorithms. Both MD5 and SHA can compress large volumes of information into a secure format, i.e., convert a string of bytes of arbitrary length into a unique integer of fixed length. Where the output of MD5 is 128 bits and the output of SHA1 in SHA is 160 bits. For example, a fingerprint of an executable file may be the MD5 value of the executable file.
The technical scheme of the invention is explained by combining the drawings and various embodiments in the specification.
Some applications are easy to decompile, so that the applications are falsified, implanted with malicious codes, packaged for the second time and forged into a counterfeit application, and the counterfeit application may have potential safety hazards, such as stealing user account passwords, privately adding advertisements, adding trojan viruses and the like.
At present, in order to realize a certain function of an application, a developer usually purchases a component product of a third-party service provider and integrates the component product into the developed application. If the function realized by the component relates to the safety aspect, and a counterfeit application integrates the component and is popularized and used, a great safety hazard is caused, so that the component needs to have the capability of identifying the real application.
Each application must be signed before it is released, and the signature mechanism is also the only verification mechanism for judging the integrity of an application. The signature mechanism cannot prevent the installation package from being modified, but the re-signature of the modified application cannot be kept consistent with the original signature. And the essence of judging whether the signatures are consistent lies in judging whether the digital certificates are consistent. The essence of comparing digital certificates lies in comparing public keys of the certificates, so that the digital certificates are different and signatures are different under the condition that the public keys are different.
Based on this, the embodiment of the application provides an application verification method and an application verification device, wherein a true unique feature code of an application is stored in a server, when the application on a terminal is started, an assembly integrated by the application interacts with the server to obtain the true unique feature code of the application, and whether the application is a counterfeit application is identified by comparing the true unique feature code with the unique feature code obtained from the application, so that the assembly can be effectively prevented from being illegally used by the counterfeit application. In this way, for the component, the digital signature of the authorized application does not need to be written in the code of the component, so that the code of the component does not need to be modified too much, the flexibility is high, and the operability is strong; for the application, the anti-counterfeiting function can be realized by integrating the components provided by the application in the prior art without excessively modifying the codes of the application, so that a convenient and fast mode is provided for deploying the anti-piracy function in the prior art.
The technical scheme provided by the application can be suitable for mobile equipment or fixed terminal equipment, such as a mobile phone, a tablet computer, a desktop computer and the like. In addition, the implementation of the technical scheme provided by the application is not limited to the operating system used by the device, and for example, the technical scheme can be applied to an Android (Android) operating system, an IOS system, a Windows system and the like.
Referring to fig. 1, fig. 1 is a flowchart of a method provided in an embodiment of the present application. Wherein the components in fig. 1 are integrated or embedded in an application and the components and the server remain network-reachable, the method is performed by the components. As shown in fig. 1, the method may include the steps of:
step 101: the server side obtains the actual unique feature code of the application with the permission to use the component function, and stores the obtained actual unique feature code on the server side.
Step 102: when an application integrated with the component on the terminal requests to call the function of the component, the component sends a unique feature code acquisition request to the server.
The component can send a unique feature code acquisition request to the server only when the application requests to use the function of the component for the first time so as to check the authority of the application, and once the application passes the authority, the verification is not needed. Or, the component may also send a unique feature code acquisition request to the server every set period, so as to check the authority of the application regularly. Or, the component may send a unique feature code acquisition request to the server every time the application requests to use the function of the component, so as to detect the authority of the application in real time.
Step 103: and the server side returns a response to the component according to the received unique feature code acquisition request.
The response returned by the server may carry a unique feature code of the application, that is, the unique feature code of the application, which is configured on the server in advance in step 101, is true.
Since a component may be integrated by multiple applications, the server needs to distinguish which application's unique signature is returned to the component.
In one possible implementation manner, the component may carry an application identifier of the application in the unique identifier obtaining request, so that the server may return the unique identifier corresponding to the application identifier, and the application identifier may be represented by a character string. Correspondingly, in this way, the server needs to configure the mapping relationship between the application identifier and the unique feature code of the application in advance.
Another possible implementation is that each application may be configured with a unique server, and the address of the server configured for the application is written in the code of the component or in the code of the application integrating the component. When the component detects the application use request, the unique feature code acquisition request is sent to the server pointed by the address, and the server returns the unique feature code stored on the server to the component after receiving the unique feature code acquisition request.
Step 104: and after the component receives a response returned by the server, if the response carries the unique feature code of the application, acquiring the unique feature code of the application from the application.
Taking the unique feature code as the public key fingerprint as an example, the implementation manner of the component acquiring the public key fingerprint of the application from the application is as follows: firstly, a component can acquire installation package information of an Application through a series of Application Programming Interfaces (APIs) of a terminal, then extract a signature of the Application from the installation package information, acquire a digital certificate of the Application through the signature, acquire a public key of the Application from the digital certificate, and finally calculate a corresponding public key fingerprint for the acquired public key according to a fingerprint algorithm agreed in advance with a server.
The fingerprint algorithm agreed by the components and the server in advance is the same as the fingerprint algorithm adopted by the server for calculating the unique feature code.
Step 105: and the component checks whether the unique characteristic code acquired from the application is consistent with the unique characteristic code returned by the server side, if so, the application is confirmed to pass the verification, and if not, the application is confirmed not to pass the verification.
A component may allow the application to use the functionality of the component when the application is confirmed to be verified.
The component may prohibit the application from using the functionality of the component when it is determined that the application has not passed the verification, or may prohibit the application from using functionality other than the component, or may prompt the application to be uninstalled.
In addition, if the response returned by the server does not carry the unique feature code of the application, for example, the response is null, which indicates that the application also does not have the authority to use the component, for example, the application is not registered with a third-party service provider who develops the component, in this case, the component may also consider that the application does not pass the verification, and the application does not have the authority to use the function of the component.
In summary, the technical scheme provided by the application can realize the function of identifying counterfeit applications by verifying whether the true unique feature code of one application is consistent with the unique feature code obtained from the application, thereby effectively preventing the assembly from being illegally used by the counterfeit applications. The component is integrated in the application, so that the unique feature code of the application can be acquired through a series of APIs provided by an official party, and considering that the real unique feature code has certain potential safety hazards no matter stored in a code of a terminal, a local database, an encrypted file and the like, once the real unique feature code is cracked, the real unique feature code is possibly modified, and counterfeit application cannot be identified, so that the real unique feature code is stored in the server, and the real unique feature code of the application is acquired through linkage of the component and the server, so that the risk that the verification certificate is tampered is reduced. In addition, the existing application can realize the anti-counterfeiting function only by integrating the components provided by the embodiment of the application without excessively modifying the codes of the application, so that a convenient mode is provided for the existing application scale deployment anti-piracy function.
The methods provided herein are described above. The apparatus provided in the present application is described below.
Referring to fig. 2, this figure is a functional block diagram of an application verification apparatus according to an embodiment of the present application. The apparatus comprises a transmitting unit 201, a receiving unit 202 and a processing unit 203.
The sending unit 201 is configured to send a unique feature code obtaining request to a server when a component integrated in an application is called by the application.
The receiving unit 202 is configured to receive a response returned by the server.
The processing unit 203 is configured to, if the response carries the unique feature code of the application, obtain the unique feature code of the application from the application; and checking whether the unique feature code acquired from the application is consistent with the unique feature code returned by the server side, if so, confirming that the application passes the verification, and otherwise, confirming that the application does not pass the verification.
Optionally, the unique feature code obtaining request may carry an application identifier of the application, so that the server returns the unique feature code corresponding to the application identifier.
Optionally, the unique feature code may be a unique feature code that is pre-configured on the server and is true to the application.
Optionally, the unique feature code may be one of the following: public key, signature, digital certificate, executable file, public key fingerprint, signature fingerprint, digital certificate fingerprint, executable file fingerprint.
Optionally, the processing unit 203 may be further configured to: and if the response returned by the server side does not carry the unique feature code of the application, confirming that the application does not pass the verification.
Optionally, if the unique feature code is a public key fingerprint, when the unique feature code of the application is acquired, the processing unit 203 is specifically configured to: acquiring installation package information of the application; extracting a signature of the application from the installation package information; acquiring a digital certificate of the application through signature; obtaining a public key of the application from the digital certificate; and calculating a corresponding public key fingerprint for the acquired public key according to a fingerprint algorithm agreed with the server side in advance.
Optionally, the fingerprint algorithm may be MD5, or SHA.
The embodiment of the application verification apparatus of the present application can be applied to any electronic device with a processor, which may be any electronic device existing, being developed, or developed in the future, including but not limited to: existing, developing or future developing desktop computers, laptop computers, mobile terminals (including smart phones, non-smart phones, various tablet computers), and the like. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. The software implementation is taken as an example, and is formed by reading corresponding computer program instructions in the storage into the memory for operation through the processor of the electronic device with the processor, which is used as a logical device. From a hardware aspect, as shown in fig. 3, a hardware structure diagram of an electronic device with a processor where a verification apparatus is applied in the present application is shown, except for the processor, the transceiver, the memory, and the storage shown in fig. 3, the electronic device with the processor where the apparatus is located in the embodiment may also include other hardware according to the actual function of the device, which is not described again.
The memory may store a logic instruction corresponding to the application verification method, and the memory may be, for example, a non-volatile memory (non-volatile memory). The processor may call the saved logic instructions in the execution memory to perform the application verification method described above.
The function of the logic instruction corresponding to the application verification method, if implemented in the form of a software functional unit and sold or used as an independent product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
As shown in fig. 3, an application verification apparatus is further provided in the embodiment of the present application, where the apparatus includes a processor 301, a transceiver 302, and a memory 303, and for example, the processor 301, the transceiver 302, and the memory 303 may be connected to each other through a bus 304.
The memory 303 is used for storing executable instructions of the processor 301.
The processor 301 is configured to:
when a component integrated in an application is called by the application, sending a unique feature code acquisition request to a server through the transceiver 302; receiving a response returned by the server through the transceiver 302; if the response carries the unique feature code of the application, acquiring the unique feature code of the application from the application; and checking whether the unique feature code acquired from the application is consistent with the unique feature code returned by the server side, if so, confirming that the application passes the verification, and otherwise, confirming that the application does not pass the verification.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.
Claims (10)
1. An application checking method, wherein the application is applied to a terminal, the application on the terminal integrates a component, and the method is applied to the component, and comprises the following steps:
when the component is called by the application integrating the component on the terminal, sending a unique feature code acquisition request to a server;
receiving a response returned by the server;
if the response carries the unique feature code of the application, and the unique feature code of the application is used for identifying whether the application is tampered or not, then
Acquiring a unique feature code of the application from the application on the terminal;
and checking whether the unique feature code acquired from the application is consistent with the unique feature code returned by the server side, if so, confirming that the application passes the verification, and otherwise, confirming that the application does not pass the verification.
2. The method of claim 1, wherein the unique feature code acquisition request carries an application identifier of the application, so that the server returns a unique feature code corresponding to the application identifier.
3. The method according to claim 1 or 2, wherein the unique signature is a unique signature of the application real configured on the server side in advance;
the unique feature code is one of the following:
public key, signature, digital certificate, executable file, public key fingerprint, signature fingerprint, digital certificate fingerprint, executable file fingerprint.
4. The method of claim 1, wherein the method further comprises:
if the response returned by the server side does not carry the unique feature code of the application, the server side sends the response to the server side
Confirming that the application fails the check.
5. The method of claim 1, wherein if the unique signature is a public key fingerprint;
the obtaining the unique feature code of the application comprises:
acquiring installation package information of the application;
extracting a signature of the application from the installation package information;
acquiring a digital certificate of the application through signature;
obtaining a public key of the application from the digital certificate;
and calculating a corresponding public key fingerprint for the acquired public key according to a fingerprint algorithm agreed with the server side in advance.
6. An application verification apparatus, comprising:
the terminal comprises a sending unit, a receiving unit and a sending unit, wherein the sending unit is used for sending a unique feature code acquisition request to a server when a component integrated in an application of the terminal is called by the application;
the receiving unit is used for receiving a response returned by the server;
a processing unit, configured to obtain a unique feature code of the application from the application on the terminal if the response carries the unique feature code of the application, and the unique feature code of the application is used to identify whether the application is tampered; and checking whether the unique feature code acquired from the application is consistent with the unique feature code returned by the server side, if so, confirming that the application passes the verification, and otherwise, confirming that the application does not pass the verification.
7. The apparatus of claim 6, wherein the unique feature code acquisition request carries an application identifier of the application, so that the server returns a unique feature code corresponding to the application identifier.
8. The apparatus according to claim 6 or 7, wherein the unique signature is a unique signature of the application real configured on the server side in advance;
the unique feature code is one of the following:
public key, signature, digital certificate, executable file, public key fingerprint, signature fingerprint, digital certificate fingerprint, executable file fingerprint.
9. The apparatus as recited in claim 6, said processing unit to further:
if the response returned by the server side does not carry the unique feature code of the application, the server side sends the response to the server side
Confirming that the application fails the check.
10. The apparatus of claim 6, wherein if the unique signature is a public key fingerprint;
when the unique feature code of the application is obtained, the processing unit is specifically configured to:
acquiring installation package information of the application;
extracting a signature of the application from the installation package information;
acquiring a digital certificate of the application through signature;
obtaining a public key of the application from the digital certificate;
and calculating a corresponding public key fingerprint for the acquired public key according to a fingerprint algorithm agreed with the server side in advance.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610971662.2A CN106529218B (en) | 2016-10-28 | 2016-10-28 | Application verification method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610971662.2A CN106529218B (en) | 2016-10-28 | 2016-10-28 | Application verification method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106529218A CN106529218A (en) | 2017-03-22 |
| CN106529218B true CN106529218B (en) | 2020-03-06 |
Family
ID=58326721
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610971662.2A Active CN106529218B (en) | 2016-10-28 | 2016-10-28 | Application verification method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106529218B (en) |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107169320A (en) * | 2017-04-20 | 2017-09-15 | 北京小米移动软件有限公司 | Method of calibration and device |
| CN107544863B (en) * | 2017-06-26 | 2021-07-20 | 新华三技术有限公司 | Data storage method and device |
| CN107480068A (en) * | 2017-08-22 | 2017-12-15 | 武汉斗鱼网络科技有限公司 | Code integrity detection method, device, electric terminal and readable storage medium storing program for executing |
| CN107943484B (en) * | 2017-11-30 | 2021-04-06 | 广州酷狗计算机科技有限公司 | Method and device for executing business function |
| CN108765621B (en) * | 2018-05-30 | 2020-11-27 | 成都天仁民防科技有限公司 | Safety inspection system and inspection method for movable operation and maintenance of civil air defense door |
| CN108846266A (en) * | 2018-07-11 | 2018-11-20 | 中国联合网络通信集团有限公司 | A kind of method, system and the communication terminal of application program operation authorization |
| CN109934016B (en) * | 2019-03-07 | 2021-11-26 | 江苏通付盾信息安全技术有限公司 | Application signature verification method and device and electronic equipment |
| CN111625781B (en) * | 2020-08-03 | 2020-11-10 | 腾讯科技（深圳）有限公司 | SDK authorization authentication method, device, equipment and storage medium |
| CN112579989B (en) * | 2020-12-23 | 2022-06-24 | 杭州安司源科技有限公司 | Anti-piracy method for network service software |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103617394A (en) * | 2013-12-04 | 2014-03-05 | 北京网秦天下科技有限公司 | SDK providing and invoking method and associated device |
| CN104182660A (en) * | 2013-05-22 | 2014-12-03 | 北大方正集团有限公司 | User equipment identification management method and system for digital right management |
| CN104199654A (en) * | 2014-08-27 | 2014-12-10 | 百度在线网络技术（北京）有限公司 | Open platform calling method and device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060064756A1 (en) * | 2004-09-17 | 2006-03-23 | Ebert Robert F | Digital rights management system based on hardware identification |
-
2016
- 2016-10-28 CN CN201610971662.2A patent/CN106529218B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104182660A (en) * | 2013-05-22 | 2014-12-03 | 北大方正集团有限公司 | User equipment identification management method and system for digital right management |
| CN103617394A (en) * | 2013-12-04 | 2014-03-05 | 北京网秦天下科技有限公司 | SDK providing and invoking method and associated device |
| CN104199654A (en) * | 2014-08-27 | 2014-12-10 | 百度在线网络技术（北京）有限公司 | Open platform calling method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106529218A (en) | 2017-03-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106529218B (en) | Application verification method and device | |
| CN101501642B (en) | Use the method for the portable mass storage of virtual machine activation | |
| US7146645B1 (en) | Dedicated applications for user stations and methods for downloading dedicated applications to user stations | |
| CN109561085B (en) | Identity verification method based on equipment identification code, server and medium | |
| JP4727278B2 (en) | Application program verification system, application program verification method, and computer program | |
| CN108683502B (en) | Digital signature verification method, medium and equipment | |
| CN109412812B (en) | Data security processing system, method, device and storage medium | |
| CN111404696B (en) | Collaborative signature method, security service middleware, related platform and system | |
| CN103827881A (en) | Method and system for dynamic platform security in a device operating system | |
| CN112257086B (en) | User privacy data protection method and electronic equipment | |
| JP4417952B2 (en) | Method and system for performing tests on devices and devices | |
| CN109614769A (en) | The secure operating system starting encapsulated according to reference platform inventory and data | |
| CN112445537B (en) | Trusted starting method and device of operating system, mobile terminal and storage medium | |
| CN108229144B (en) | Verification method of application program, terminal equipment and storage medium | |
| CN111191195A (en) | Method and device for protecting APK | |
| CN109117605B (en) | Authentication method, device and equipment thereof and storage medium | |
| KR20170089352A (en) | Firmware integrity verification for performing the virtualization system | |
| KR101642267B1 (en) | System for preventing forgery of application and method therefor | |
| JP2007094879A (en) | Authentication system for basic program of operating system, computer used for the same, and computer program | |
| KR20070059891A (en) | Application authentication security system and method thereof | |
| CN110602051B (en) | Information processing method based on consensus protocol and related device | |
| CN111611551B (en) | Dynamic link library protection method and system based on cryptographic algorithm | |
| CN113094708A (en) | Electronic file processing method and device, storage medium and processor | |
| CN108259490B (en) | Client verification method and device | |
| KR101906484B1 (en) | Method for application security and system for executing the method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Applicant after: Xinhua three Technology Co., Ltd. Address before: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Applicant before: Huasan Communication Technology Co., Ltd. |
|
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |