CN102087689B - Method and device for protecting software reused module - Google Patents

Abstract

In order to solve the problem that there is no corresponding protection scheme at the software reuse module level in the prior art, the present invention discloses a protection method and device for a software reuse module. The method disclosed in the present invention includes: according to the first key and the The identification of the application program that reuses the module authority, generates the first encryption result and generates the registration code of the reuse module, and when the application program that needs to use the reuse module runs, obtains the registration code of the reuse module, the identification of the application program and the obtained key according to the first key The reuse module verification code, obtain the first key through the reuse module verification code, generate the second encryption result according to the first key and the obtained identification, obtain the first encryption result according to the registration code, and compare the first encryption result and the second encryption result The result of the second encryption determines whether the application program has the authority to use the reuse module. It is precisely because the authority verification is realized through the registration code and the check code, and then the software is protected at the level of the software reuse module.

Description

A method and device for protecting a software reuse module

technical field

The invention belongs to the technical field of digital encryption, in particular to a protection method and device for a software reuse module.

Background technique

Software reuse is the basic idea and method of software development in software engineering, and reuse means using existing results. In the process of software development, we found that most of the content in the development is relatively mature, and only a small part of the work is innovative. We can consider mature work to be high-quality and reusable, and our productivity can be improved by reusing these mature works.

Reasonably split the mature and reusable work in development to form high-cohesion and low-coupling modules, so that these independent modules that can provide complete functions can be used in other software development. These modules are It's called a reusable module. The extracted software modules are continuously added to the reusable module library. When some reusable modules are needed, the reusable modules you need can be directly extracted from the module library and accumulated like "building blocks", so that commonly used software can be easily formed.

With the rapid development of computer software, there will be more and more software modularization, and many reusable modules will be used in software products. How to protect these reusable modules from being abused and protect software at the level of software reusable modules has not yet been corresponding solution.

Contents of the invention

In order to solve the problem that there is no corresponding protection scheme at the software reuse module level in the prior art, an embodiment of the present invention provides a protection method for software reuse modules, including:

According to the first key and the identification of the application program with the authority to use the reuse module, use the encryption algorithm to generate the first encryption result, and generate the registration code of the reuse module according to the first encryption result, and the first key is obtained according to the private key of the reuse module key;

When the application program that needs to use the reuse module is running, obtain the registration code of the reuse module, the identification of the application program and the check code of the reuse module obtained according to the first key added in the reuse module;

The first key is obtained by reusing the module verification code, and the second encryption result is generated by using an encryption algorithm according to the first key and the identifier obtained when the application program is running;

The first encryption result is obtained through the registration code of the reuse module, and according to the same result of the first encryption and the second encryption result, it is determined that the application program that needs to use the reuse module has the permission to use the reuse module, otherwise, there is no permission to use the module.

At the same time, the embodiment of the present invention also provides a protection device for a software reuse module, including:

The first generation module: used to generate the first encryption result by using an encryption algorithm according to the first key and the identification of the application program with the authority to use the reuse module, and generate the registration code of the reuse module according to the first encryption result, the first key is based on Reuse the module private key to get the key;

Obtaining module: used to obtain the registration code of the reused module, the identification of the application and the checksum of the reused module obtained from the first key added in the reused module when the application program that needs to use the reused module is running;

The second generation module: used to obtain the first key by reusing the module verification code, and generate a second encryption result by using an encryption algorithm according to the first key and the identifier obtained when the application program is running;

Authority determination module: used to obtain the first encryption result through the registration code of the reuse module. According to the same result of the first encryption and the second encryption result, it is determined that the application program that needs to use the reuse module has the authority to use the reuse module, otherwise, there is no use authority.

It can be seen from the specific implementation scheme provided by the present invention that the authorization verification is realized through the reuse module registration code and the reuse module verification code, and then the software is protected at the level of the software reuse module.

Description of drawings

Fig. 1 is the method flowchart of the first embodiment provided by the present invention;

Fig. 2 is the flow chart of the registration code and verification code generation method of the first embodiment provided by the present invention;

Fig. 3 is a flow chart of the second encryption result generation method of the first embodiment provided by the present invention;

Fig. 4 is a flow chart of the method for generating the first encryption result according to the first embodiment of the present invention;

Fig. 5 is a structural diagram of the device of the second embodiment provided by the present invention.

Detailed ways

In order to solve the problem in the prior art that there is no corresponding protection scheme at the level of software reuse modules, the embodiment of the present invention provides a protection method for software reuse modules. When an application program needs to use a certain reuse module, then You need to apply for a reuse module registration code. When using a reuse module, you need to provide the identification of the application, such as: application process name, etc. The generation of the reuse module registration code requires the following steps: obtain the identification ID1 of the application program with the permission to use the reuse module, generate the first encrypted result crytoText by using an encryption algorithm according to KEY1 and ID1, and generate the reuse module registration code licenseCode according to crytoText. The key KEY1 may directly use the reuse module private key moduleKey, or may use the encrypted result moduleKeyHash obtained by irreversibly encrypting the reuse module private key moduleKey. Regardless of whether moduleKey or moduleKeyHash is used as KEY1, the key KEY1 is obtained according to the private key moduleKey of the reused module. After the reuse module registration code licenseCode is generated, an association between application 1 and licenseCode needs to be established so that the licenseCode can be obtained when application 1 is running. Add the reuse module verification code moduleCode and verification program segment at the use entry of the reuse module, so that when it is called by application 1, it can verify the usage permission of the calling application through the carried moduleCode. moduleCode can directly use moduleKey, The character-encoded moduleKeyHash can also be used. When the application 1 is running, the licenseCode, the ID1' of the application 1 and the moduleCode carried by the reused module are obtained. After application 1 invokes the reuse module, it verifies the usage authority of the calling application through the carried moduleCode. The verification process is as follows: the reuse module obtains the key KEY1 (moduleKey or moduleKeyHash) through the moduleCode, and according to the key KEY1 and the application 1 The ID1' obtained during operation uses an encryption algorithm to generate a second encryption result hcNumber.

According to the licenseCode obtained when the application 1 is running, the crytoText is obtained. According to the same crytoText and licNumber, it is determined that the application 1 has the permission to use the reuse module, otherwise, there is no permission to use it.

The first embodiment provided by the present invention is a method for protecting a software reuse module, and the XML editor is a multimedia text editor used as an application program. One of the core modules in the XML editor is the modification trace module. As an independent module, it is not only used in the XML editor, but also frequently used in other application modules. The modification trace module is used as a reuse in the embodiment of the present invention. module, the following assumes that the XML editor is an application program that has the permission to use the reuse module, and after the modification trace reuse module is used by an application program, verify the application program that uses it to determine whether the program is an XML editor that has the permission to use the module To explain in detail, the method flow is shown in Figure 1, including:

Step 101: Use the private key moduleA of the modification trace reuse module A to symmetrically encrypt the XMLEditor logo XMLEditor to generate crytoText, use crytoText as the registration code licenseCode of the modification trace reuse module A, and use moduleA as the certificate of the modification trace reuse module A Check code moduleCode.

Step 102: Add moduleCode at the use entry of the modification trace reuse module A, so that when it is called, the authority verification of the calling application is performed through the moduleCode.

Step 103: When the application program 1 is running, obtain the crytoText as the licenseCode, the ID1' of the application program 1, and the moduleA as the moduleCode added in the modification trace reuse module A.

Step 104: Use the moduleA carried by the modification trace reuse module A to perform symmetric encryption on the ID1' to generate the second encryption result licNumber.

Step 105: According to the same crytoText and licNumber, it is determined that the application program 1 has the right to use the reuse module, otherwise, it does not have the right to use.

In step 101, generating licenseCode and moduleCode can also be shown in Figure 2. Specifically, the process of generating crytoText can also be irreversible encryption (one-way encryption) to the private key moduleA of the modification trace reuse module A to obtain moduleKeyHash, Irreversibly encrypt the XMLEditor ID of the XML editor to obtain appIdHash, and use moduleKeyHash as a key to symmetrically encrypt appIdHash to generate crytoText. In this embodiment, hash operation is used to realize irreversible encryption. Both the moduleKey and the moduleKeyHash function as a key in this embodiment, that is, the key KEY1 obtained from the reused module private key moduleKey. The function of the key KEY1 is to generate crytoText together with the mark XMLEditor. The encryption of XMLEditor and moduleA is one-way, which ensures that crytoText cannot be cracked, and enhances the security of reusing module A with modification traces. Furthermore, the licenseCode and moduleCode can also be obtained in the following way, using a random number as a key to perform symmetric encryption on crytoText, and the encrypted result is represented by cryptoRandKey. Use random numbers to encrypt crytoText to ensure that the registration code generated by the modification trace reuse module A is different each time. Concatenate the generated cryptoRandKey with the random number used in the previous step to form licCode, and use character encoding to generate visible characters from licCode and moduleKeyHash to form licenseCode and moduleCode.

In step 102, it is also possible to add the moduleCode generated by moduleKeyHash using character encoding to the use entry of the modification trace reuse module A, whether moduleA is directly used as the verification code moduleCode of the modification trace reuse module A, or moduleKeyHash The moduleCode is generated by character encoding, and the moduleCode is obtained according to the key KEY1.

In step 103, obtain the moduleA added as the moduleCode in the modification trace reuse module A. It can also be, if the moduleCode generated by moduleKeyHash using character encoding is added to the usage entry of the modification trace reuse module A in the preceding steps, then The modification trace reuse module A called at this time carries the moduleCode generated by encoding the moduleKeyHash using character encoding, and the obtained licenseCode is the licenseCode obtained by encrypting the random number.

Since the relationship between application 1 and licenseCode was previously established, for example, add licenseCode to the configuration file related to application 1, or add licenseCode to the string resource of the resource file related to application 1, or write licenseCode to Entrance to Application 1. Therefore, the specific implementation of acquiring the licenseCode may be that when the application program 1 is running, a module that performs subsequent authority verification, such as a dongle, can obtain the licenseCode by reading the configuration file carrying the licenseCode. Alternatively, the dongle reads the resource file with the licenseCode added in the character string resource to obtain the licenseCode. Alternatively, write the licenseCode to the entry of application 1, and when application 1 is running, the dongle will directly obtain the licenseCode from application 1. The dongle registers the obtained licenseCode in the memory for use in subsequent steps.

Wherein step 104, the process that the second encryption result licNumber generates can also be, as shown in Figure 3, the moduleCode (moduleCode is that moduleKeyHash uses the mode of character encoding to generate after moduleKeyHash is encoded) carried by modification trace reuse module A, obtains moduleKeyHash, The identifier ID1' is irreversibly encrypted to obtain appIdHash', and the appIdHash' is symmetrically encrypted using moduleKeyHash to generate a second encryption result licNumber. No matter which method is used to finally obtain the second encryption result licNumber, the key KEY1 is obtained through the moduleCode, and the second encryption result licNumber is obtained together with the identifier ID1'. Here, whether the key KEY1 is moduleKeyHash or moduleA, its function is to obtain the second encryption result licNumber together with the ID ID1'.

If the licenseCode obtained after encryption with random numbers is used, before step 105, the crytoText needs to be obtained according to the licenseCode, as shown in Figure 4. Specifically, the licenseCode is decoded, and the licenseCode is converted into licCode, and the random code and the licCode are separated from the licCode. cryptoRandKey, the random code is used as the key, and the cryptoRandKey is decrypted to generate crytoText. During specific implementation, crytoText can be inserted into the registration code sequence of the application, and used when waiting for comparison with licNumber.

For step 105, it is determined that crytoText and licNumber are the same, either by directly comparing crytoText and licNumber to determine that they are the same, or, before step 105, using a random number (identical to the random number used to encrypt crytoText) as a key pair The licNumber performs symmetric encryption, splicing the encrypted result and the random number to obtain a splicing result, and uses character encoding to generate visible characters to form the final registration comparison code, and compares the registration comparison code with the licenseCode, according to the comparison result Same, make sure crytoText and licNumber are the same.

The second embodiment provided by the present invention is a protection device for a software reuse module, the structure of which is shown in Figure 5, including:

The first generation module 201: used to generate the first encryption result by using an encryption algorithm according to the first key and the identification of the application program with the authority to use the reuse module, and generate the registration code of the reuse module according to the first encryption result. The first key is Obtain the key according to the private key of the reuse module;

Obtaining module 202: used to acquire the registration code of the reused module, the identification of the application and the checksum of the reused module obtained according to the first key added in the reused module when the application program that needs to use the reused module is running;

The second generation module 203: used to obtain the first key by reusing the module verification code, and generate a second encryption result by using an encryption algorithm according to the first key and the identification obtained when the application program is running;

Authority determination module 204: used to obtain the first encryption result through the reuse module registration code, and determine that the application program that needs to use the reuse module has the authority to use the reuse module according to the same first encryption result and the second encryption result, otherwise, there is no use authority .

Further, the first generating module 201: is also used to use the one-way encrypted private key of the reuse module as the first key, and perform symmetric encryption on the identifier of the application program having the right to use the reuse module after the one-way encryption to obtain The first encrypted result.

Further, it also includes:

Check code generation module 205: used to use the private key of the reuse module after one-way encryption as the first key, and use the visible characters generated by character encoding as the check code of the reuse module;

The second generating module 203: used to decode the characters of the reuse module check code to obtain the reuse module private key after one-way encryption, and use the one-way encryption reuse module private key to encrypt the application after one-way encryption The identity obtained when the program is running is symmetrically encrypted to obtain a second encryption result.

Further, the first generation module 201: is also used to use the random number as a key to perform symmetric encryption on the first encryption result to obtain a third encryption result;

Splicing the third encryption result and the random number, and using the visible characters generated by the splicing result using character encoding as the reuse module registration code;

Authority determination module 204: is also used to perform character decoding on the reuse module registration code, separate the third encryption result and random number from the decoded reuse module registration code, use the random number as a key to decrypt the third encryption result, and obtain The first encrypted result.

Further, the first generation module 201: is also used to use the visible characters generated by the first encryption result in a character encoding manner as the reuse module registration code;

The authority determination module 204 is further configured to perform character decoding on the registration code of the reuse module to obtain a first encryption result.

Further, the first generation module 201: is also used to use the private key of the reuse module as the first key, perform symmetric encryption on the identification of the application program with the authority to use the reuse module to obtain the first encryption result, and use the first encryption result as the reuse Module registration code;

The authority determining module 204: is further configured to use the reuse module registration code as the first encryption result.

Further, it also includes:

Verification code generation module 205: used to use the reuse module private key as the reuse module verification code;

The second generating module 203 is used to use the private key of the reuse module as the first key, and use the private key of the reuse module to symmetrically encrypt the identifier obtained when the application program is running to obtain a second encryption result.

Further, the acquisition module 202: is also used to read the configuration file carrying the registration code of the reuse module to obtain the registration code of the reuse module when the application program that needs to use the reuse module is running; or

When the application that needs to use the reuse module is running, read the resource file with the registration code of the reuse module added in the string resource to obtain the registration code of the reuse module; or

When the application program that needs to use the reuse module is running, the registration code of the reuse module newly added in the application program that needs to use the reuse module is read to obtain the registration code of the reuse module.

Further, the authority determination module 204: is further configured to determine that the two are the same based on a direct comparison between the first encryption result and the second encryption result.

Further, the authority determining module 204: is further configured to use a random number as a key to perform symmetric encryption on the second encryption result to obtain a fourth encryption result;

Splicing the fourth encryption result and the random number, and using the visible characters generated by the character encoding method of the splicing result as the reuse module registration comparison code; according to comparing the reuse module registration code and the reuse module registration comparison code, determine the first encryption result and the second encryption result The two encryption results are the same.

Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalent technologies, the present invention also intends to include these modifications and variations.

Claims (16)

1. A protection method for a software reuse module, comprising: According to the first key and the identification of the application program with permission to use the reuse module, use an encryption algorithm to generate a first encryption result, and generate a reuse module registration code according to the first encryption result, the first key is obtained according to the private key of the reuse module key; When the application program that needs to use the reuse module is running, obtain the registration code of the reuse module, the identification of the application program and the check code of the reuse module obtained according to the first key added in the reuse module; The first key is obtained by reusing the module verification code, and the second encryption result is generated by using an encryption algorithm according to the first key and the identifier obtained when the application program is running; The first encryption result is obtained through the registration code of the reuse module, and according to the same result of the first encryption and the second encryption result, it is determined that the application program that needs to use the reuse module has the permission to use the reuse module, otherwise, there is no permission to use the module. 2. The method according to claim 1, characterized in that, according to the first key and the identification of the application program with permission to use the reuse module, using an encryption algorithm to generate the first encryption result is specifically: Using the one-way encrypted reuse module private key as the first key, perform symmetric encryption on the one-way encrypted application program identification with the right to use the reuse module to obtain a first encryption result. 3. The method according to claim 2, wherein obtaining the reuse module verification code according to the first key is specifically: The private key of the reusable module after one-way encryption as the first key, and the visible characters generated by character encoding as the reusable module verification code; The first key is obtained by reusing the module verification code, and the second encryption result is generated using an encryption algorithm based on the first key and the identifier obtained when the application is running: The reuse module check code is decoded to obtain the one-way encrypted reuse module private key, and the one-way encrypted reuse module private key is used to symmetric the identity obtained when the one-way encrypted application is running. The encryption yields a second encrypted result. 4. The method according to claim 3, wherein generating the reuse module registration code according to the first encryption result is specifically: using a random number as a key to symmetrically encrypt the first encryption result to obtain a third encryption result; Splicing the third encryption result and the random number, and using the visible characters generated by the splicing result using character encoding as the reuse module registration code; The first encryption result obtained by reusing the module registration code is as follows: Perform character decoding on the reuse module registration code, separate the third encryption result and random number from the decoded reuse module registration code, use the random number as a key to decrypt the third encryption result, and obtain the first encryption result. 5. The method according to claim 3, wherein generating the reuse module registration code according to the first encryption result is specifically: using the visible characters generated by the first encryption result using character encoding as the reuse module registration code; The first encryption result obtained by reusing the module registration code is as follows: Character decoding is performed on the reuse module registration code to obtain a first encrypted result. 6. The method according to claim 1, characterized in that, according to the first key and the identification of the application program with permission to use the reuse module, an encryption algorithm is used to generate a first encryption result, and a reuse module registration is generated according to the first encryption result The code is specifically: Using the private key of the reuse module as the first key, symmetrically encrypting the identification of the application program with the authority to use the reuse module to obtain a first encryption result, and using the first encryption result as the registration code of the reuse module; The first encryption result obtained by reusing the module registration code is as follows: The reuse module registration code is used as the first encryption result. 7. The method according to claim 6, wherein the verification code obtained according to the first key is specifically: Use the reuse module private key as the reuse module verification code; The first key is obtained by reusing the module verification code, and the second encryption result is generated using an encryption algorithm based on the first key and the identifier obtained when the application is running: The private key of the reuse module is used as the first key, and the identifier obtained when the application program is running is symmetrically encrypted by using the private key of the reuse module to obtain a second encryption result. 8. The method according to claim 1, characterized in that, when the application program that needs to use the reuse module is running, obtaining the registration code of the reuse module is specifically: When the application program that needs to use the reuse module is running, read the configuration file carrying the registration code of the reuse module to obtain the registration code of the reuse module; or When the application that needs to use the reuse module is running, read the resource file with the registration code of the reuse module added in the string resource to obtain the registration code of the reuse module; or When the application program that needs to use the reuse module is running, the registration code of the reuse module newly added in the application program that needs to use the reuse module is read to obtain the registration code of the reuse module. 9. The method according to claim 1, wherein according to the fact that the first encryption result is identical to the second encryption result is: determining that the first encryption result and the second encryption result are identical based on a direct comparison. 10. The method according to claim 4, wherein, according to the fact that the first encryption result is the same as the second encryption result, it is specifically: Using a random number as a key to perform symmetric encryption on the second encryption result to obtain a fourth encryption result; Splicing the fourth encryption result and the random number, and using the visible characters generated by the character encoding method of the splicing result as the reuse module registration comparison code; according to comparing the reuse module registration code and the reuse module registration comparison code, determine the first encryption result and the second encryption result The two encryption results are the same. 11. A protection device for a software reuse module, comprising: The first generation module: used to generate the first encryption result by using an encryption algorithm according to the first key and the identification of the application program with the authority to use the reuse module, and generate the registration code of the reuse module according to the first encryption result, the first key is based on Reuse the module private key to get the key; Obtaining module: used to obtain the registration code of the reused module, the identification of the application and the checksum of the reused module obtained from the first key added in the reused module when the application program that needs to use the reused module is running; The second generation module: used to obtain the first key by reusing the module verification code, and generate a second encryption result by using an encryption algorithm according to the first key and the identifier obtained when the application program is running; Authority determination module: used to obtain the first encryption result through the registration code of the reuse module. According to the same result of the first encryption and the second encryption result, it is determined that the application program that needs to use the reuse module has the authority to use the reuse module, otherwise, there is no use authority. 12. The device according to claim 11, wherein the first generation module is further configured to use the private key of the reuse module after one-way encryption as the first key, and use the one-way encrypted Symmetric encryption is performed on the identification of the application program that reuses the module authority to obtain a first encryption result. 13. The device according to claim 12, further comprising a verification code generation module: used to generate the private key of the reuse module after performing one-way encryption as the first key by means of character encoding The visible characters are used as the reuse module check code; The second generation module: it is also used to decode the characters of the reuse module check code to obtain the private key of the reuse module after one-way encryption, and use the private key of the reuse module after one-way encryption to encrypt the application The identity obtained when the program is running is symmetrically encrypted to obtain a second encryption result. 14. The device according to claim 13, wherein the first generating module is further configured to use a random number as a key to symmetrically encrypt the first encryption result to obtain a third encryption result; Splicing the third encryption result and the random number, and using the visible characters generated by the splicing result using character encoding as the reuse module registration code; Authority Determination Module: It is also used to decode the characters of the reuse module registration code, separate the third encryption result and random number from the decoded reuse module registration code, use the random number as a key to decrypt the third encryption result, and obtain the third encryption result An encrypted result. 15. The device according to claim 11, wherein the first generation module is further configured to use the private key of the reuse module as the first key to symmetrically encrypt the identification of the application program with the permission to use the reuse module to obtain The first encryption result, using the first encryption result as the reuse module registration code; Authority determination module: it is also used to use the reuse module registration code as the first encryption result. 16. The device according to claim 15, further comprising a verification code generation module: used to use the reuse module private key as the reuse module verification code; The second generation module: it is also used to use the private key of the reuse module as the first key, and use the private key of the reuse module to symmetrically encrypt the identifier obtained when the application program is running to obtain a second encryption result.

Images