CN107135077B - Software protection method and device - Google Patents

Abstract

Embodiments of the present invention provide a software protection method and device. The method includes: the node in the peer-to-peer network receives the signature information sent by the software development platform; the signature information sent by the software development platform is verified according to the public key of the software developer; if the node verifies the signature information sent by the software development platform according to the public key of the software developer, If the sent signature information is successfully verified, the second hash value is calculated according to the historical hash value and the random number; if the second hash value is less than the threshold, the node sends the identity information of the software developer, the identification information of the software to be released, The first hash value, the random number and the second hash value are sent to other nodes in the peer-to-peer network. The embodiment of the present invention prevents illegal nodes from modifying the software, and at the same time can conveniently determine whether the software has been modified according to the hash value corresponding to the software identification, thereby improving the protection of the software.

Description

Software protection method and device

technical field

The embodiments of the present invention relate to the field of communication technologies, and in particular, to a software protection method and device.

Background technique

The Web is widely popularized, and people use various Web applications. These Web application services bring great convenience to people's work and life, and promote the development of society. However, with the rapid development of web applications, the information leakage and economic losses caused by attacks on web application vulnerabilities are increasing. Software tampering has become the biggest threat to web systems.

In order to solve this problem, some technical solutions have been proposed in the prior art to prevent the software from being tampered with, one of which is: divide the content of software or information products into local information and network information and store them on independent media and network centers respectively A legal user has a unique identification information; the network center runs an application software, which can judge whether the user is legal through the identification information transmitted by the user, and transmit the required network information to the legal user. The content of the software is not easy to be illegally copied, thereby effectively preventing piracy, and even eliminating piracy, and can be used for application software or information products on the market. This invention is mainly that after the user has a legal identification, the software can be downloaded from the network. In addition, there is another way: according to the received software control command, generate the corresponding first software characteristic character string; use the first software characteristic character string as the decryption key to decrypt the pre-stored encrypted image file to obtain the corresponding Decrypt the image file; load the decrypted image file, and judge whether the decrypted image file can be loaded normally; if so, the software recognizes it as not tampered with; if not, the software recognizes it as tampered with. It replaces the traditional use of verification strings to identify whether software has been tampered with with decrypted image files for identification, making the identification process no longer dependent on independent verification strings, and the identification process is more intuitive and does not require manual comparison.

However, there is a problem in the above technical solution that the protection of software is not strong enough.

Contents of the invention

Embodiments of the present invention provide a software protection method and device, so as to improve the strength of software protection.

An aspect of the embodiments of the present invention is to provide a software protection method, including:

The nodes in the peer-to-peer network receive the signature information sent by the software development platform. The signature information is the identity information of the software developer, the identification information of the software to be released, and the first hash information of the software development platform using its corresponding private key. The information obtained after the hash value is signed;

The node obtains the public key of the software developer by querying historical records according to the identity information of the software developer;

The node verifies the signature information sent by the software development platform according to the public key of the software developer;

If the node successfully verifies the signature information sent by the software development platform according to the public key of the software developer, then calculates the second hash value according to the historical hash value and the random number;

If the second hash value is less than the threshold, the node will use the identity information of the software developer, the identification information of the software to be released, the first hash value, the random number, and the second The hash value is sent to other nodes in the peer-to-peer network.

Another aspect of the embodiments of the present invention provides a software protection device, including:

The receiving module is used to receive the signature information sent by the software development platform, and the signature information is the identity information of the software developer, the identification information of the software to be released, and the first hash of the software development platform using its corresponding private key. The information obtained after the value is signed;

A query module, configured to query historical records to obtain the public key of the software developer according to the identity information of the software developer;

A verification module, configured to verify the signature information sent by the software development platform according to the public key of the software developer;

A calculation module, configured to calculate a second hash value according to historical hash values and random numbers when the signature information sent by the software development platform is successfully verified according to the public key of the software developer;

A sending module, configured to send the identity information of the software developer, the identification information of the software to be released, the first hash value, the random number, and the The second hash value is sent to other nodes in the peer-to-peer network.

The software protection method and device provided by the embodiments of the present invention receive the signature information sent by the software development platform through the nodes in the peer-to-peer network, and verify the signature information according to the public key of the software developer; if the verification is successful, the node Calculate a new hash value based on the historical hash value and random number. If the new hash value is less than the threshold, the node will share the identity information of the software developer, the identification information of the software to be released, the random number and the new hash value. The value is sent to other nodes in the peer-to-peer network to prevent illegal nodes from modifying the software. At the same time, according to the hash value corresponding to the software identification, it can be conveniently determined whether the software has been modified, which improves the protection of the software.

Description of drawings

FIG. 1 is a flowchart of a software protection method provided by an embodiment of the present invention;

FIG. 2 is a network architecture diagram applicable to the software protection method provided by the embodiment of the present invention;

FIG. 3 is a structural diagram of a software protection device provided by an embodiment of the present invention;

FIG. 4 is a structural diagram of a software protection device provided by another embodiment of the present invention.

Detailed ways

FIG. 1 is a flowchart of a software protection method provided by an embodiment of the present invention; FIG. 2 is a network architecture diagram applicable to the software protection method provided by an embodiment of the present invention. The specific software protection method steps are as follows:

Step S101, the nodes in the peer-to-peer network receive the signature information sent by the software development platform, the signature information is the identity information of the software developer, the identification information of the software to be released, The information obtained after the first hash value is signed.

As shown in Figure 2, when the software development platform releases a piece of software, it simultaneously releases the identity information of the software developer, the identification information of the software to be released, the software to be released, and the first hash value, the first hash value It is the hash value obtained by the software development platform performing hash operations on the identity information of the software developer, the identification information of the software to be released, and the software to be released. For example, the software development platform sends the identity information of the software developer, the identification information of the software to be released, the software to be released, and the first hash value to the application server. Wherein, the identity information of the software developer may specifically be the name of the software developer, the identification information of the software to be released may specifically be the name of the software to be released, and the software to be released may specifically be the software to be released after being developed by the software developer. itself. In order to prevent malicious modifiers from modifying the software while calculating a new HASH value so that the verifier cannot detect it, while releasing the software, the software development platform also needs to share the identity information of the software developer, the identification information of the software to be released, and the first hash value. The hash value is published to the public ledger, which is maintained by each node in the peer-to-peer network, and the public ledger is guaranteed not to be tampered with. In addition, the software development platform can also be a node in the peer-to-peer network.

When the user terminal queries the software itself from the application server, it obtains the identity information of the software developer corresponding to the software itself, the identification information of the software to be released, and the first hash value; Obtain the first hash value corresponding to the software itself from the public ledger in . The user terminal compares whether the first hash value corresponding to the software itself obtained from the application server is consistent with the first hash value corresponding to the software itself obtained from the public ledger. If not, the user terminal does not download the software itself ; If consistent, the user terminal downloads the software itself. After the user terminal downloads the software itself, the identity information of the software developer, the identification information of the software to be released, and the software to be released are hashed to obtain a hash value, and compare whether the calculated hash value is consistent with the first hash value corresponding to the software itself recorded in the application server and the public ledger. If they are not consistent, the user terminal will not install or use the software itself. If they are consistent, Then the user terminal installs or uses the software itself.

Specifically, the software development platform can use its corresponding private key to sign the identity information of the software developer, the identification information of the software to be released, and the first hash value to obtain the signature information, and send the signature information to the peer-to-peer network. of nodes.

Step S102, the node searches history records according to the identity information of the software developer to obtain the public key of the software developer.

In this embodiment, the public ledger can also record the correspondence between the identity information of each node and the public key of each node, for example, it can record the identity information of the software developer and the public key of the software developer.

After receiving the signature information sent by the software development platform, the nodes in the peer-to-peer network query the public key of the software developer corresponding to the identity information of the software developer in the public ledger.

Step S103, the node verifies the signature information sent by the software development platform according to the public key of the software developer.

The nodes in the peer-to-peer network verify the signature information sent by the software development platform according to the software developer's public key.

Step S104, if the node successfully verifies the signature information sent by the software development platform according to the public key of the software developer, calculate a second hash value according to the historical hash value and the random number.

If the node in the peer-to-peer network successfully verifies the signature information sent by the software development platform according to the public key of the software developer, it means that the identity of the software developer is true and legal, then the node will use the historical hash value and random number Calculate the second hash value. When the node calculates the second hash value, other nodes in the peer-to-peer network are also calculating the second hash value. The purpose of each node in the peer-to-peer network to calculate the second hash value is : Each node obtains the right to record the identity information of the software developer, the identification information of the software to be released, and the first hash value according to the calculated second hash value. Specifically, if one of the nodes calculates If the second hash value obtained is less than the threshold, the node can obtain the right to record the identity information of the software developer, the identification information of the software to be released, and the first hash value.

Step S105, if the second hash value is less than the threshold, the node sends the identity information of the software developer, the identification information of the software to be released, the first hash value, the random number and the The second hash value is sent to other nodes in the peer-to-peer network.

If the second hash value is less than the threshold, the node sends the identity information of the software developer, the identification information of the software to be released, the first hash value, the random number and the second hash value to other nodes in the peer-to-peer network.

In the embodiment of the present invention, the node in the peer-to-peer network receives the signature information sent by the software development platform, and verifies the signature information according to the public key of the software developer; Calculate a new hash value, if the new hash value is less than the threshold, the node will send the identity information of the software developer, the identification information of the software to be released, the random number and the new hash value to the peer-to-peer network Other nodes prevent illegal nodes from modifying the software, and at the same time, it can be conveniently determined whether the software has been modified according to the hash value corresponding to the software identification, which improves the protection of the software.

On the basis of the above-mentioned embodiments, a node in the peer-to-peer network can also send its own identity information and the node's public key to other nodes in the peer-to-peer network, so that other nodes can combine the node's identity information and the node's public key The public key is stored in the public ledger. In addition, before the node receives the signature information sent by the software development platform, the node can also receive the corresponding relationship between the software developer's identity information and the software developer's public key sent by the software development platform; The corresponding relationship between the developer's identity information and the software developer's public key is stored in the history record.

FIG. 3 is a structural diagram of a software protection device provided by an embodiment of the present invention. The software protection device provided by the embodiment of the present invention can execute the processing flow provided by the embodiment of the software protection method. As shown in FIG. 35, wherein the receiving module 31 is configured to receive the signature information sent by the software development platform, the signature information is the identity information of the software developer, the identification information of the software to be released, The information obtained after the first hash value is signed; the query module 32 is used to query the historical records to obtain the public key of the software developer according to the identity information of the software developer; the verification module 33 is used to develop the software according to the software developer. The public key of the software developer verifies the signature information sent by the software development platform; when the calculation module 34 is used to verify the signature information sent by the software development platform according to the public key of the software developer successfully, according to the historical hash value and the random number to calculate the second hash value; the sending module 35 is used to send the identity information of the software developer, the identification information of the software to be released, the first hash value when the second hash value is less than the threshold Send the hash value, the random number and the second hash value to other nodes in the peer-to-peer network.

In the embodiment of the present invention, the node in the peer-to-peer network receives the signature information sent by the software development platform, and verifies the signature information according to the public key of the software developer; Calculate a new hash value, if the new hash value is less than the threshold, the node will send the identity information of the software developer, the identification information of the software to be released, the random number and the new hash value to the peer-to-peer network Other nodes prevent illegal nodes from modifying the software, and at the same time, it can be conveniently determined whether the software has been modified according to the hash value corresponding to the software identification, which improves the protection of the software.

FIG. 4 is a structural diagram of a software protection device provided by another embodiment of the present invention. On the basis of the above embodiments, the first hash value is the hash value obtained by the software development platform performing hash operations on the identity information of the software developer, the identification information of the software to be released, and the software to be released. Greek value.

The first hash value is a hash value obtained by the software development platform performing a hash operation on the identity information of the software developer, the identification information of the software to be released, and the software to be released.

The sending module 35 is also configured to send the node's identity information and the node's public key to other nodes in the peer-to-peer network. The receiving module 31 is also used to receive the corresponding relationship between the identity information of the software developer sent by the software development platform and the public key of the software developer; in addition, the software protection device 30 also includes a storage module 36, the storage module 36 and storing the corresponding relationship between the software developer's identity information and the software developer's public key in the history record.

The software protection device provided by the embodiment of the present invention can be specifically used to execute the method embodiment provided in FIG. 1 above, and the specific functions will not be repeated here.

In the embodiment of the present invention, the node in the peer-to-peer network receives the signature information sent by the software development platform, and verifies the signature information according to the public key of the software developer; Calculate a new hash value, if the new hash value is less than the threshold, the node will send the identity information of the software developer, the identification information of the software to be released, the random number and the new hash value to the peer-to-peer network Other nodes prevent illegal nodes from modifying the software, and at the same time, it can be conveniently determined whether the software has been modified according to the hash value corresponding to the software identification, which improves the protection of the software.

To sum up, the embodiment of the present invention receives the signature information sent by the software development platform through the nodes in the peer-to-peer network, and verifies the signature information according to the public key of the software developer; Hash value and random number to calculate a new hash value, if the new hash value is less than the threshold, the node will send the identity information of the software developer, the identification information of the software to be released, the random number and the new hash value to Other nodes in the peer-to-peer network prevent illegal nodes from modifying the software, and at the same time, it is convenient to determine whether the software has been modified according to the hash value corresponding to the software identification, which improves the protection of the software.

In the several embodiments provided by the present invention, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware, or in the form of hardware plus software functional units.

The above-mentioned integrated units implemented in the form of software functional units may be stored in a computer-readable storage medium. The above-mentioned software functional units are stored in a storage medium, and include several instructions to make a computer device (which may be a personal computer, server, or network device, etc.) or a processor (processor) execute the methods described in various embodiments of the present invention. partial steps. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other various media that can store program codes. .

Those skilled in the art can clearly understand that for the convenience and brevity of description, only the division of the above-mentioned functional modules is used as an example for illustration. The internal structure of the system is divided into different functional modules to complete all or part of the functions described above. For the specific working process of the device described above, reference may be made to the corresponding process in the foregoing method embodiments, and details are not repeated here.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present invention, rather than limiting them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: It is still possible to modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements for some or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the technical solutions of the various embodiments of the present invention. scope.

Claims (10)

1. a kind of software protecting method characterized by comprising

Node in peer-to-peer network receives the signing messages that Software Development Platform is sent, and the signing messages is the software development Platform is using its corresponding private key to the identity information of software developer, the identification information of software to be released, the first cryptographic Hash The information obtained after being signed；

Identity information of the node according to the software developer, the public affairs of the query history record acquisition software developer Key；

The node is verified according to the signing messages that the public key of the software developer sends the Software Development Platform；

If the signing messages verifying that the node sends the Software Development Platform according to the public key of the software developer at Function then calculates the second cryptographic Hash according to history cryptographic Hash and random number；

If second cryptographic Hash is less than threshold value, the node is by the identity information of the software developer, to be released soft The identification information of part, first cryptographic Hash, the random number and second cryptographic Hash are sent in the peer-to-peer network Other nodes.

2. the method according to claim 1, wherein first cryptographic Hash is the Software Development Platform to institute It states the identity information of software developer, the identification information of software to be released, software to be released and carries out what Hash operation obtained Cryptographic Hash.

3. according to the method described in claim 2, it is characterized in that, the identity information of the software developer, to be released soft The identification information of part, software to be released and first cryptographic Hash storage are on the application server.

4. according to the method described in claim 3, it is characterized by further comprising:

The public key of the identity information of the node and the node is sent to other sections in the peer-to-peer network by the node Point.

5. the method according to claim 1, wherein the node receives the A.L.S. that Software Development Platform is sent Before breath, further includes:

The node receive the software developer that the Software Development Platform is sent identity information and the software development The corresponding relationship of the public key of person；

The corresponding relationship of the identity information of the software developer and the public key of the software developer is stored in by the node In the historical record.

6. a kind of software safeguards, which is characterized in that applied to the node in peer-to-peer network, comprising:

Receiving module, for receiving the signing messages of Software Development Platform transmission, the signing messages is that the software development is flat Platform using its corresponding private key to the identity information of software developer, the identification information of software to be released, the first cryptographic Hash into The information obtained after row signature；

Enquiry module, for the identity information according to the software developer, query history record obtains the software developer Public key；

Authentication module, for being carried out according to the public key of the software developer to the signing messages that the Software Development Platform is sent Verifying；

Computing module, for being verified according to the public key of the software developer to the signing messages that the Software Development Platform is sent When success, the second cryptographic Hash is calculated according to history cryptographic Hash and random number；

Sending module, for when second cryptographic Hash is less than threshold value, by the identity information of the software developer, to be released Identification information, first cryptographic Hash, the random number and second cryptographic Hash of software be sent to the peer-to-peer network In other nodes.

7. software safeguards according to claim 6, which is characterized in that first cryptographic Hash is the software development Platform carries out Hash fortune to the identity information of the software developer, the identification information of software to be released, software to be released Obtained cryptographic Hash.

8. software safeguards according to claim 7, which is characterized in that the identity information of the software developer, to The identification information of the software of publication, software to be released and first cryptographic Hash storage are on the application server.

9. software safeguards according to claim 8, which is characterized in that the sending module is also used to the node Identity information and the public key of the node be sent to other nodes in the peer-to-peer network.

10. software safeguards according to claim 6, which is characterized in that the receiving module is also used to receive institute State the corresponding relationship of the identity information of the software developer of Software Development Platform transmission and the public key of the software developer；

The software safeguards further include memory module, and the memory module is used for the identity information of the software developer It is stored in the historical record with the corresponding relationship of the public key of the software developer.