CN115906016A

CN115906016A - Source code protection method, device, equipment and storage medium

Info

Publication number: CN115906016A
Application number: CN202111111283.3A
Authority: CN
Inventors: 田新超; 黄亚洲; 郭建强; 后江振
Original assignee: 360 Digital Security Technology Group Co Ltd
Current assignee: 360 Digital Security Technology Group Co Ltd
Priority date: 2021-09-22
Filing date: 2021-09-22
Publication date: 2023-04-04

Abstract

The invention belongs to the technical field of computers, and discloses a source code protection method, a source code protection device, source code protection equipment and a storage medium. The method comprises the steps of acquiring encryption key information corresponding to a source code to be encrypted; encrypting and packaging the source code to be encrypted according to the encryption key information to obtain a ciphertext source code packet; and generating ciphertext key data according to the encryption key information, and adding the ciphertext key data to the ciphertext source code packet. Because the encryption key information corresponding to the source code to be encrypted is used for encryption and packaging when the source code to be encrypted of the Electron application is packaged, the generated ciphertext source code packet needs to be decrypted according to the encryption key information obtained by decrypting the ciphertext key data added to the ciphertext source code packet to obtain the Electron application source code, the source code cracking difficulty is improved, and the safety risk of the Electron application is reduced.

Description

Source code protection method, device, equipment and storage medium

Technical Field

The present invention relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a storage medium for source code protection.

Background

The Web technology is one of the most widely applied technologies in the field of software development nowadays, and the surrounding ecology is prosperous and has a long history. Electron is a framework for creating native programs using Web technologies such as JavaScript, HTML, and CSS. And combining Chromium and node.js into the same runtime environment, and packaging the same into application under a Mac, windows or Linux system to realize cross-platform running of software.

The source code of the application software adopting Electron as a basic framework is usually packed into an installation package of the application in a plain text or ASAR (an unencrypted packing format) mode, and is stored in a plain text mode in an installation catalog of the application. Because the source code is not protected by the Electron application, the Electron application software faces a higher security risk than the traditional C + +/C compiled binary client program.

The above is only for the purpose of assisting understanding of the technical solution of the present invention, and does not represent an admission that the above is the prior art.

Disclosure of Invention

The invention mainly aims to provide a source code protection method, a source code protection device, source code protection equipment and a source code protection storage medium, and aims to solve the technical problem that electronic application software in the prior art has higher safety risk.

In order to achieve the above object, the present invention provides a source code protection method, which comprises the following steps:

acquiring encryption key information corresponding to a source code to be encrypted;

encrypting and packaging the source code to be encrypted according to the encryption key information to obtain a ciphertext source code packet;

and generating ciphertext key data according to the encryption key information, and adding the ciphertext key data to the ciphertext source code packet.

Optionally, before the step of obtaining the encryption key information corresponding to the source code to be encrypted, the method further includes:

when a source code operation instruction sent by a user is received, acquiring the instruction type of the source code operation instruction;

if the instruction type is a source code packaging type, determining a source code access path according to the source code operation instruction;

and reading the source code to be encrypted according to the source code access path.

Optionally, after the step of obtaining the instruction type of the operation instruction when the operation instruction sent by the user is received, the method further includes:

when the instruction type is a source code loading instruction, searching a data packet to be loaded according to the source code operating instruction;

extracting cipher key data in the data packet to be loaded;

decrypting the ciphertext key data through a preset module public key to obtain encrypted key information;

and decrypting the data packet to be loaded according to the decryption key information to obtain an application source code, and loading the application source code.

Optionally, before the step of obtaining the instruction type of the operation instruction when the operation instruction sent by the user is received, the method further includes:

when a software starting instruction is received, determining target software according to the software starting instruction;

running the target software and monitoring a source code operation interface of the target software;

and when detecting that the source code operation interface is called, taking an instruction for calling the source code operation interface as a source code operation instruction.

Optionally, the step of running the target software and monitoring a source code operation interface of the target software includes:

acquiring an installation path of the target software;

running the target software based on the installation path;

and monitoring a source code operation interface of the target software when the target software is successfully operated.

Optionally, the step of obtaining the installation path of the target software includes:

detecting whether the target software is installed;

if the target software is not installed, acquiring a downloading path of the target software;

downloading the software installation package of the target software according to the downloading path, and carrying out security verification on the software installation package;

when the security verification passes, installing the target software according to the software installation package;

and when the installation is finished, acquiring the installation path of the target software.

Optionally, the step of downloading the software installation package of the target software according to the download path and performing security verification on the software installation package includes:

downloading the software installation package of the target software according to the download path, and extracting signature data in the software installation package;

decrypting the signature data through a preset signature verification public key to obtain standard verification data;

performing abstract calculation on the software installation package according to a preset abstract algorithm to obtain software verification data;

and when the standard verification data is consistent with the software verification data, judging that the security verification is passed.

Optionally, after the step of running the target software based on the installation path, the method further includes:

starting a state monitoring thread when the target software is successfully operated;

monitoring the process running state of the target software through the state monitoring thread;

and when the process running state of the target software is monitored to be a debugged state, ending the software process of the target software.

monitoring a source code debugging interface of the target software when the target software successfully runs;

when the source code debugging interface is called, obtaining debugging configuration parameters corresponding to the target software;

determining whether source code debugging is allowed or not according to the debugging configuration parameters;

and if the source code debugging is not allowed, interrupting the calling of the source code debugging interface.

Optionally, the step of performing encryption and packaging on the source code to be encrypted according to the encryption key information to obtain a ciphertext source code packet includes:

packaging the source code to be encrypted to obtain a source code resource packet;

determining a source code encryption algorithm and encryption parameters according to the encryption key information;

and encrypting the source code resource packet based on the source code encryption algorithm and the encryption parameters to obtain a ciphertext source code packet.

Optionally, the step of generating ciphertext key data according to the encryption key information and adding the ciphertext key data to the ciphertext source code packet includes:

encrypting the encrypted key information through a preset module private key to obtain ciphertext key data;

and adding the ciphertext key data into a file header of the ciphertext source code packet.

Optionally, the step of obtaining encryption key information corresponding to the source code to be encrypted includes:

acquiring source code identification information corresponding to the source code to be encrypted;

searching a corresponding configuration record in a preset source code encryption configuration table according to the source code identification information;

and determining encryption key information corresponding to the source code to be encrypted according to the configuration record.

In addition, in order to achieve the above object, the present invention further provides a source code protection device, where the source code protection device includes the following modules:

the information acquisition module is used for acquiring encryption key information corresponding to the source code to be encrypted;

the source code processing module is used for carrying out encryption and packaging on the source code to be encrypted according to the encryption key information to obtain a ciphertext source code packet;

and the ciphertext adding module is used for generating ciphertext key data according to the encryption key information and adding the ciphertext key data to the ciphertext source code packet.

Optionally, the information obtaining module is further configured to obtain an instruction type of the source code operation instruction when the source code operation instruction sent by the user is received; if the instruction type is a source code packaging type, determining a source code access path according to the source code operation instruction; and reading the source code to be encrypted according to the source code access path.

Optionally, the source code processing module is further configured to, when the instruction type is a source code loading instruction, search for a data packet to be loaded according to the source code operating instruction; extracting cipher key data in the data packet to be loaded; decrypting the ciphertext key data through a preset module public key to obtain encrypted key information; and decrypting the data packet to be loaded according to the decryption key information to obtain an application source code, and loading the application source code.

Optionally, the information obtaining module is further configured to determine the target software according to the software starting instruction when the software starting instruction is received; running the target software and monitoring a source code operation interface of the target software; and when detecting that the source code operation interface is called, taking an instruction for calling the source code operation interface as a source code operation instruction.

Optionally, the information obtaining module is further configured to obtain an installation path of the target software; running the target software based on the installation path; and monitoring a source code operation interface of the target software when the target software is successfully operated.

Optionally, the information obtaining module is further configured to detect whether the target software is installed; if the target software is not installed, acquiring a download path of the target software; downloading the software installation package of the target software according to the downloading path, and carrying out security verification on the software installation package; when the security verification passes, installing the target software according to the software installation package; and when the installation is completed, acquiring the installation path of the target software.

In addition, to achieve the above object, the present invention further provides a source code protection device, including: a processor, a memory and a source code protection program stored on the memory and executable on the processor, the source code protection program when executed implementing the steps of the source code protection method as described above.

In addition, in order to achieve the above object, the present invention further provides a computer-readable storage medium, where a source code protection program is stored, and when the source code protection program is executed, the steps of the source code protection method are implemented.

The method comprises the steps of acquiring encryption key information corresponding to a source code to be encrypted; encrypting and packaging the source code to be encrypted according to the encryption key information to obtain a ciphertext source code packet; and generating ciphertext key data according to the encryption key information, and adding the ciphertext key data to the ciphertext source code packet. Because the encryption key information corresponding to the source code to be encrypted is used for encryption and packaging when the source code to be encrypted of the Electron application is packaged, the generated ciphertext source code packet needs to be decrypted according to the encryption key information obtained by decrypting the ciphertext key data added to the ciphertext source code packet to obtain the Electron application source code, the source code cracking difficulty is improved, and the safety risk of the Electron application is reduced.

Drawings

Fig. 1 is a schematic structural diagram of an electronic device in a hardware operating environment according to an embodiment of the present invention;

FIG. 2 is a flowchart illustrating a source code protection method according to a first embodiment of the present invention;

FIG. 3 is a flowchart illustrating a source code protection method according to a second embodiment of the present invention;

FIG. 4 is a flowchart illustrating a source code protection method according to a third embodiment of the present invention;

fig. 5 is a block diagram of a source code protection device according to a first embodiment of the present invention.

The implementation, functional features and advantages of the present invention will be further described with reference to the accompanying drawings.

Detailed Description

It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

Referring to fig. 1, fig. 1 is a schematic structural diagram of a source code protection device of a hardware operating environment according to an embodiment of the present invention.

As shown in fig. 1, the electronic device may include: a processor 1001, such as a Central Processing Unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. Wherein a communication bus 1002 is used to enable connective communication between these components. The user interface 1003 may include a Display screen (Display), an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a Wireless interface (e.g., a Wireless-Fidelity (WI-FI) interface). The Memory 1005 may be a Random Access Memory (RAM) or a Non-Volatile Memory (NVM), such as a disk Memory. The memory 1005 may alternatively be a storage device separate from the processor 1001.

Those skilled in the art will appreciate that the configuration shown in fig. 1 does not constitute a limitation of the electronic device and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.

As shown in fig. 1, a memory 1005, which is a kind of storage medium, may include therein an operating system, a network communication module, a user interface module, and a source code protection program.

In the electronic device shown in fig. 1, the network interface 1004 is mainly used for data communication with a network server; the user interface 1003 is mainly used for data interaction with a user; the processor 1001 and the memory 1005 in the electronic device of the present invention may be disposed in a source code protection device, and the electronic device calls a source code protection program stored in the memory 1005 through the processor 1001 and executes the source code protection method provided in the embodiment of the present invention.

An embodiment of the present invention provides a source code protection method, and referring to fig. 2, fig. 2 is a schematic flow diagram of a first embodiment of a source code protection method according to the present invention.

In this embodiment, the source code protection method includes the following steps:

step S100: and acquiring encryption key information corresponding to the source code to be encrypted.

It should be noted that the execution main body of this embodiment may be the source code protection device, and the source code protection device may be an electronic device such as a personal computer, a tablet computer, and the like, and may also be other devices that can achieve the same or similar functions.

It should be noted that the source code to be encrypted may be an Electron application source code that needs to be protected. The encryption key information may be key information used when the source code to be encrypted is encrypted, the encryption key information may include information such as a source code encryption algorithm, an encryption parameter, and the like, and the encryption key information may be preset by a manager of the source code protection device. The source code encryption algorithm may be a symmetric encryption algorithm, for example: SM1, SMS4, or DES, 3DES, TDEA, and other symmetric encryption algorithms. The encryption parameter may be a parameter that is input to a source encryption algorithm for increasing encryption complexity in encryption.

Further, if the encryption key information used by all the source codes to be encrypted during encryption is the same, the encryption rule is easy to be found, and different encryption key information can be set for different source codes in order to improve the difficulty of finding the encryption rule, and at this time, this embodiment step S100 may include:

and determining the encryption key information corresponding to the source code to be encrypted according to the configuration record.

The source code identification information may be a unique identifier for distinguishing different source codes, and may be identification information such as a project name of a source code or a source code access path. The searching for the corresponding configuration record in the preset source encryption configuration table according to the source identifier information may be searching for the corresponding configuration record in the preset source configuration table by using the source identifier information as a query parameter, where the preset source configuration table may be a database table composed of multiple configuration records, and the configuration record in the preset source configuration table may be preset by an administrator of the source protection device or a user using the source protection device. The preset source code configuration table may be stored locally in the source code protection device, or may be stored in a remote server, which is not limited in this embodiment. The configuration record may include data such as source code identification information, source code encryption algorithms, encryption parameters, and the like. Determining the encryption key information corresponding to the source code to be encrypted according to the configuration data may be analyzing the configuration data, and extracting a source code encryption algorithm and an encryption parameter in the configuration data, thereby obtaining the encryption parameter corresponding to the source code to be encrypted.

Step S200: and encrypting and packaging the source code to be encrypted according to the encryption key information to obtain a ciphertext source code packet.

It should be noted that, the source code to be encrypted is encrypted and packaged according to the encryption key information, and the ciphertext source code packet is obtained by selecting a corresponding source code encryption algorithm and an encryption parameter according to the encryption key information, encrypting the source code to be encrypted according to the source code encryption algorithm and the encryption parameter, and then packaging, or packaging the source code to be encrypted and then encrypting.

In actual use, the packaging tool can be modified, and the modified packaging tool is used for carrying out encryption packaging on the source codes to be encrypted according to the encryption key information to obtain the ciphertext source code packet, wherein the packaging tool can be a packaging tool provided by an Electron framework.

Further, in order to improve the efficiency of encrypting the ciphertext source code packet, in this embodiment, the step S200 may include:

It should be noted that, the source code to be encrypted is packaged, and the obtaining of the source code resource package may be to package the source code to be encrypted by using a modified packaging tool. Determining the source code encryption algorithm and the encryption parameters according to the encryption key information may be reading data in the encryption key information to obtain the source code encryption algorithm and the encryption parameters. The source code resource packet is encrypted based on the source code encryption algorithm and the encryption parameters, and the ciphertext source code packet is obtained by inputting the encryption parameters and the source code resource packet into the source code encryption algorithm for encryption.

It can be understood that the source code applied generally includes a large number of source code files, if the source code files are encrypted and then packaged, the source code files need to be encrypted circularly during encryption, and a large amount of resources are consumed to be called and generated in the circulating process, so that the overall execution speed is slow, the encrypted source code is packaged firstly, and the source code resource package is integrally encrypted after the source code resource package is obtained, so that a large number of circulating operations can be avoided, and further, the efficiency of encrypting the ciphertext source code package can be greatly improved.

Step S300: and generating ciphertext key data according to the encryption key information, and adding the ciphertext key data to the ciphertext source code packet.

It should be noted that, the generating of the ciphertext key data according to the encryption key information may be encrypting the encryption key information to generate the ciphertext key data. The adding of the ciphertext key data to the ciphertext source code packet may be adding the ciphertext key data to a target file region of the ciphertext source code packet, where the target file region may be set in advance by an administrator of the source code protection device or a user using the source code protection device.

Further, in order to reduce the possibility of cracking the key data of the ciphertext and reduce the complexity of normally parsing the ciphertext source code packet, the step S300 in this embodiment may include:

encrypting the encrypted key information through a preset module private key to obtain ciphertext key data; and adding the ciphertext key data into a file header of the ciphertext source code packet.

It should be noted that the preset module private key may be an encrypted private key assigned to the packaging tool when the packaging tool is modified. The preset module private key is used for encrypting the encryption key information to obtain the ciphertext key data, the preset information encryption algorithm is used for encrypting the encryption key, the ciphertext data generated after encryption is used as the ciphertext key data, and the preset information encryption algorithm can be an asymmetric encryption algorithm, for example: RSA, elgamal, etc.

It can be understood that data encrypted according to an encryption private key through an asymmetric encryption algorithm can be normally decrypted only according to a public key corresponding to the encryption private key, and the decryption difficulty is very high, so that encrypted file information is encrypted by adopting a preset module private key when ciphertext key data are generated, the possibility of decrypting the ciphertext key data can be greatly reduced, a file head of the file is generally located at the beginning of the file, the acquisition difficulty is low, the ciphertext key data can be extracted from the file head of a fast ciphertext source code packet when the ciphertext source code packet needs to be analyzed, the complexity of normally analyzing the ciphertext source code packet can be reduced, and the normal analysis efficiency is improved.

In the embodiment, encryption key information corresponding to a source code to be encrypted is obtained; encrypting and packaging the source code to be encrypted according to the encryption key information to obtain a ciphertext source code packet; and generating ciphertext key data according to the encryption key information, and adding the ciphertext key data to the ciphertext source code packet. Because the encryption key information corresponding to the source code to be encrypted is used for encryption and packaging when the source code to be encrypted of the Electron application is packaged, the generated ciphertext source code packet needs to be decrypted according to the encryption key information obtained by decrypting the ciphertext key data added to the ciphertext source code packet to obtain the Electron application source code, the source code cracking difficulty is improved, and the safety risk of the Electron application is reduced.

Referring to fig. 3, fig. 3 is a flowchart illustrating a source code protection method according to a second embodiment of the present invention.

Based on the first embodiment, before the step S100, the source code protection method in this embodiment further includes:

step S10: and when a source code operation instruction sent by a user is received, acquiring the instruction type of the source code operation instruction.

It should be noted that the source code operation instruction may be an instruction sent to the source code protection device by the user when the user needs to operate the source code. The instruction types of the source code operation instruction can be divided into a source code packaging type, a source code loading type, a source code checking type, a source code modification type and the like.

In practical use, a specific type parameter may be set in the source code operation instruction, and the type parameter is used to distinguish different types of instructions, for example: assuming that the type parameter is type, when the type parameter type in the source code operation instruction = package, the instruction type of the source code operation instruction is a source code packing type; when the type parameter type = load in the source code operation instruction, the instruction type of the source code operation instruction is a source code loading type; when the type parameter type = view in the source code operation instruction, the instruction type of the source code operation instruction is a source code view instruction; when the type parameter type = update in the source code operation instruction, the instruction type of the source code operation instruction is a source code modification instruction.

Step S20: and if the instruction type is a source code packaging type, determining a source code access path according to the source code operation instruction.

It should be noted that, if the instruction type is a source code packaging type, it indicates that the user packages the source codes into the application installation package, and at this time, the user specifies the source codes to be packaged by setting a source code access path in the source code operation instruction, so that when the instruction type is the source code packaging type, the source code access path may be read from the source code operation instruction.

Step S30: and reading the source code to be encrypted according to the source code access path.

It should be noted that the source code access path may be a local access path or a remote access path. If the source code access path is a local access path, it indicates that the source code to be packaged is stored locally in the source code protection device, and at this time, the source code to be encrypted can be directly read according to the source code access path. If the source code access path is a remote access path, it indicates that the source codes to be packaged are stored in the remote server, and at this time, a source code acquisition request may be sent to the remote server storing the source codes according to the source code access path, and the source codes to be encrypted are read from a source code acquisition response fed back by the remote server.

Further, since the packaging tool is modified correspondingly, and the modified packaging tool is different from the ordinary packaging tool when packaging, in order to ensure that the modified packaging tool can be loaded normally to perform the packaged application installation package, after step S01, the method may further include:

extracting ciphertext key data in the data packet to be loaded;

The source code loading instruction may be an instruction sent by a user to the source code protection device when the application installation package needs to be loaded. The data package to be loaded may be an application installation package that needs to be loaded. The searching for the data packet to be loaded according to the source code operation instruction may be searching for a corresponding data packet to be loaded according to a data packet access path in the source code operation instruction. Extracting the ciphertext key data in the to-be-loaded data packet may be reading data in a target file region in the to-be-loaded data packet to obtain the ciphertext key data, for example: and if the target file area is a file header, reading data in the file header of the data packet to be loaded to obtain key data of the ciphertext. The preset module public key may be an encrypted public key which is distributed to the unpacking tool corresponding to the packing tool when the packing tool is modified and corresponds to the preset module private key, and the ciphertext key data encrypted by the preset module private key can be decrypted by the preset module public key. And decrypting the data packet to be loaded according to the decryption key information to obtain an application source code, wherein the step of loading the application source code can be to determine a source code encryption algorithm and an encryption parameter according to the decryption key information, select a source code decryption algorithm corresponding to the source code encryption algorithm, decrypt the data packet to be loaded through the source code decryption algorithm and the encryption parameter to obtain the application source code, and load the loading source code into a memory of the source code protection device.

In the embodiment, when a source code operation instruction sent by a user is received, the instruction type of the source code operation instruction is obtained; if the instruction type is a source code packaging type, determining a source code access path according to the source code operation instruction; and reading the source code to be encrypted according to the source code access path. When a source code operation instruction sent by a user is received, whether the source code is packaged or the application source code is loaded can be determined according to the instruction type of the source code operation instruction, so that the source code protection method can meet the actual use requirement of the user.

Referring to fig. 4, fig. 4 is a schematic flowchart illustrating a source code protection method according to a third embodiment of the present invention.

Based on the second embodiment, before the step S10, the source code protection method in this embodiment further includes:

step S01: and when a software starting instruction is received, determining target software according to the software starting instruction.

The target software may be Electron software or other software. When the user needs to start the target software, the user can send a software starting instruction to the source code protection device. And determining that the target software can be the software identifier in the software starting instruction according to the software starting instruction, and searching corresponding software in the source code protection device according to the software identifier.

Step S02: and running the target software and monitoring a source code operation interface of the target software.

It should be noted that the source code operation interface may be a functional interface provided by the target software for performing corresponding operation on the source code. After the target software is run, the interface monitoring thread can be started, and the source code operation interface of the target software is monitored through the interface monitoring thread.

Further, in order to ensure that the target software can normally run, step S02 in this embodiment may include:

acquiring an installation path of the target software;

running the target software based on the installation path;

It should be noted that software generally needs to be installed before running in a device, even if the software is partially installation-free, an installation package needs to be decompressed in the device, and files after decompression are stored in a corresponding directory, and an installation path may be an access path of an installation directory of the software in the device or an access path of a directory stored in files after decompression of the installation package. The running of the target software based on the installation path may be to record an installation directory of the installation path open target software or a directory in which decompressed files are saved, and run a start program of the target software stored in the directory, thereby running the target software. The source code operation interface of the monitoring target software can be a starting interface monitoring thread, and the source code operation interface of the target software is monitored through the interface monitoring thread.

Further, the target software may not be installed in advance, and in order to ensure that the target software can run normally, the step of acquiring the installation path of the target software according to this embodiment may include:

detecting whether the target software is installed;

if the target software is not installed, acquiring a download path of the target software;

It should be noted that, the detecting whether the target software is installed or not may be to find whether registration information corresponding to the target software exists in a registry of the source code protection device, determine that the target software is installed when the registration information corresponding to the target software exists in the registry, and determine that the target software is not installed when the frowning information corresponding to the target software does not exist in the registry. It may be determined whether the target software has been installed by searching the device for the presence of a file decompressed by the installation package in which the target software is stored in the stored directory.

It can be understood that, if the target software needs to be installed in order to ensure that the target software can normally operate, the download path of the target software may be acquired at this time. The obtaining of the download path of the target software may be searching for the download path of the target software in a preset software path mapping table, where the preset software path mapping table may store mapping relationships between the software and the download path of the software, and the preset software path mapping table may be preset by a manager of the source code protection device, or may be provided by a third-party organization. The security check of the software installation package may be to detect whether the software installation package is tampered, and the installation target software may be to run the software installation package for installation according to the software installation package, or to decompress the software installation package into a preset folder.

It can be understood that, if the security check passes, it indicates that the software installation package is not tampered, so that the target software can be installed directly according to the software installation package, and after the installation is completed, the installation path of the target software can be obtained.

Further, in order to quickly determine whether the software installation package is tampered with, the step of performing security check on the software installation package may include:

downloading the software installation package of the target software according to the downloading path, and extracting signature data in the software installation package;

It should be noted that, extracting signature data in the software installation package may be reading data of a specific area in the software installation package to obtain signature data, for example: and reading data in the file header of the software installation package to obtain signature data. Or reading the data stored in the signature file in the software installation package to obtain the signature data. The signature data may be data generated by a publishing server of the software installation package signing the software installation package.

In practical use, the publishing server extracts the digest data of the software installation package through a preset digest algorithm, and then encrypts the digest data through a signature algorithm preset in the server, so as to obtain signature data, wherein the preset digest algorithm may be a hash algorithm, for example: MD5 or SHA, etc. The signature algorithm can be SM2 national password asymmetric algorithm or other asymmetric algorithms, and a private key used by the signature algorithm is stored in the issuing server.

It should be noted that the standard verification data may be digest data of the software installation package used when the remote server generates the signature data. The preset signature verification public key may be a public key corresponding to a private key used by a signature algorithm in the issuing server, and may be preset by a manager of the source code protection device. By calculating the abstract data of the software installation package, the calculation speed is extremely high, the abstract data obtained by calculating the same file is the same, and whether the software installation package is falsified or not can be quickly determined by comparing the standard verification data obtained by decrypting the signature data in the software installation package with the software verification data obtained by performing the abstract calculation on the software installation package by the source code protection device.

It can be understood that, if the standard verification data is consistent with the software verification data, it indicates that the software installation package issued by the issuing server is consistent with the software installation package received by the source code protection device, and the software installation package is not tampered, so that it can be determined that the security verification passes.

Further, in order to avoid that an attacker cracks the application in the target software through a code cracking tool to obtain a source code of the application, and ensure the security of the source code of the application, after the step of running the target software based on the installation path in this embodiment, the method may further include:

It should be noted that, a cracking tool usually uses a debugger to attach to a debugged process, and analyzes internal logic of a program by tracking execution conditions of assembly instructions of the debugged program, and to avoid debugging of target software by the debugger of the cracking tool, a state monitoring thread may be started when the target software successfully runs, and a process running state of the target software is detected by the state monitoring thread.

In actual use, the monitoring of the process running state of the target software through the state monitoring thread may be to acquire a preset interval duration, periodically acquire process parameters of a software process of the target software through the state monitoring thread with the preset interval duration as a period, and determine the process running state of the target software through the process parameters. For different systems, the manner of detecting whether the process state of the target software is the debugged state is also different, for example: if the system is a Windows system, the judgment can be carried out by detecting the value corresponding to the Beingdebugged member in the PEB (Process Environment Block) of the software process of the target software, and if the corresponding value is 1, the running state of the process of the target software is a debugged state; if the system is a Linux system, the state/proc/self/status of the software process of the target software can be detected, wherein the TracerPid indicates the debugger process id, and if the value corresponding to the TracerPid is not 0, the process running state of the target software is a debugged state; if the system is a Mac system, whether the process running state of the target software is a debugged state can be judged by inquiring the ptrace state of the kinfo _ proc in the software process of the target software.

It can be understood that, if the process running state of the target software is a debugged state, it indicates that the application in the target software may be being cracked by the cracking tool, and therefore, the software process of the target software can be ended, and the running of the software process of the target software is interrupted, thereby preventing the source code of the application in the target software from being cracked.

Further, in order to avoid that an attacker cracks the application in the target software through code debugging, obtains a source code of the application, and ensures the security of the source code of the application, after the step of running the target software based on the installation path in this embodiment, the method may further include:

when the source code debugging interface is called, acquiring debugging configuration parameters corresponding to the target software;

It should be noted that the debugging configuration parameter may be a configuration parameter set by an administrator of the source code protection device to declare whether code debugging is allowed. The source code debugging interface can be a debugging mode starting interface provided by the Electron, the access path can be webcontexts. Opendevtools (), the debugging mode can be started when the source code debugging interface is called, and the codes and logic of the Electron application can be tracked in a single line, so that the source codes of the Electron application can be obtained. Therefore, when the source code debugging interface is detected to be called, the debugging configuration parameters corresponding to the target software can be obtained, whether source code debugging is allowed or not is determined according to the debugging configuration parameters, and if the source code debugging is not allowed, the code debugging is forbidden by a manager of the source code protection equipment, so that the terminal can call the source code debugging interface and the debugging mode is forbidden to be started.

Step S03: and when detecting that the source code operation interface is called, taking an instruction for calling the source code operation interface as a source code operation instruction.

It can be understood that, if the source code operation interface is called, it indicates that the user needs to operate the source code, and sends a source code operation instruction to the source code protection device, and the source code operation interface is called by the source code operation instruction, so that the instruction calling the source code operation interface can be used as the source code operation instruction.

The embodiment determines the target software according to the software starting instruction when the software starting instruction is received; running the target software and monitoring a source code operation interface of the target software; and when detecting that the source code operation interface is called, taking an instruction for calling the source code operation interface as a source code operation instruction. Because the user can quickly operate the target software according to the software starting instruction when sending the software starting instruction, and the source code operation interface of the target software can be monitored after the target software is operated, the user can quickly respond to the operation of the source code operation interface when calling the source code operation interface, the operation of the user is simplified, and the convenience of the source code protection method is improved.

In addition, an embodiment of the present invention further provides a storage medium, where a source code protection program is stored on the storage medium, and the source code protection program, when executed by a processor, implements the steps of the source code protection method described above.

Referring to fig. 5, fig. 5 is a block diagram illustrating a first embodiment of a source code protection apparatus according to the present invention.

As shown in fig. 5, a source code protection apparatus provided in the embodiment of the present invention includes:

the information acquisition module 10 is configured to acquire encryption key information corresponding to a source code to be encrypted;

the source code processing module 20 is configured to perform encryption and packaging on the source code to be encrypted according to the encryption key information to obtain a ciphertext source code packet;

and the ciphertext adding module 30 is configured to generate ciphertext key data according to the encryption key information, and add the ciphertext key data to the ciphertext source code packet.

Further, the information obtaining module 10 is further configured to obtain an instruction type of the source code operation instruction when receiving the source code operation instruction sent by the user; if the instruction type is a source code packaging type, determining a source code access path according to the source code operation instruction; and reading the source code to be encrypted according to the source code access path.

Further, the source code processing module 20 is further configured to, when the instruction type is a source code loading instruction, search for a data packet to be loaded according to the source code operation instruction; extracting cipher key data in the data packet to be loaded; decrypting the ciphertext key data through a preset module public key to obtain encryption key information; and decrypting the data packet to be loaded according to the decryption key information to obtain an application source code, and loading the application source code.

Further, the information obtaining module 10 is further configured to determine target software according to a software starting instruction when the software starting instruction is received; running the target software and monitoring a source code operation interface of the target software; and when detecting that the source code operation interface is called, taking an instruction for calling the source code operation interface as a source code operation instruction.

Further, the information obtaining module 10 is further configured to obtain an installation path of the target software; running the target software based on the installation path; and monitoring a source code operation interface of the target software when the target software is successfully operated.

Further, the information obtaining module 10 is further configured to detect whether the target software is installed; if the target software is not installed, acquiring a downloading path of the target software; downloading the software installation package of the target software according to the downloading path, and carrying out security verification on the software installation package; when the security verification passes, installing the target software according to the software installation package; and when the installation is finished, acquiring the installation path of the target software.

Further, the information obtaining module 10 is further configured to download a software installation package of the target software according to the download path, and extract signature data in the software installation package; decrypting the signature data through a preset signature verification public key to obtain standard verification data; performing abstract calculation on the software installation package according to a preset abstract algorithm to obtain software verification data; and when the standard verification data is consistent with the software verification data, judging that the security verification is passed.

Further, the information obtaining module 10 is further configured to start a state monitoring thread when the target software successfully runs; monitoring the process running state of the target software through the state monitoring thread; and when the process running state of the target software is monitored to be a debugged state, ending the software process of the target software.

Further, the information obtaining module 10 is further configured to monitor a source code debugging interface of the target software when the target software successfully runs; when the source code debugging interface is called, obtaining debugging configuration parameters corresponding to the target software; determining whether source code debugging is allowed or not according to the debugging configuration parameters; and if the source code debugging is not allowed, interrupting the calling of the source code debugging interface.

Further, the source code processing module 20 is further configured to pack the source code to be encrypted to obtain a source code resource packet; determining a source code encryption algorithm and encryption parameters according to the encryption key information; and encrypting the source code resource packet based on the source code encryption algorithm and the encryption parameters to obtain a ciphertext source code packet.

Further, the ciphertext adding module 30 is further configured to encrypt the encrypted key information through a preset module private key to obtain ciphertext key data; and adding the ciphertext key data into a file header of the ciphertext source code packet.

Further, the information obtaining module 10 is further configured to obtain source code identification information corresponding to the source code to be encrypted; searching a corresponding configuration record in a preset source code encryption configuration table according to the source code identification information; and determining the encryption key information corresponding to the source code to be encrypted according to the configuration record.

It should be understood that the above is only an example, and the technical solution of the present invention is not limited in any way, and in a specific application, a person skilled in the art may set the technical solution as needed, and the present invention is not limited thereto.

It should be noted that the above-described work flows are only exemplary, and do not limit the scope of the present invention, and in practical applications, a person skilled in the art may select some or all of them to achieve the purpose of the solution of the embodiment according to actual needs, and the present invention is not limited herein.

In addition, the technical details that are not described in detail in this embodiment may refer to the source code protection method provided in any embodiment of the present invention, and are not described herein again.

Further, it is to be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrases "comprising a," "8230," "8230," or "comprising" does not exclude the presence of other like elements in a process, method, article, or system comprising the element.

The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention or portions thereof that contribute to the prior art may be embodied in the form of a software product, where the computer software product is stored in a storage medium (e.g. a Read Only Memory (ROM)/RAM, a magnetic disk, and an optical disk), and includes several instructions for enabling a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to execute the method according to the embodiments of the present invention.

The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.

The invention discloses A1 and a source code protection method, wherein the source code protection method comprises the following steps:

A2, the source code protection method according to A1, before the step of obtaining the encryption key information corresponding to the source code to be encrypted, further includes:

A3, the source code protection method as described in A2, further including, after the step of obtaining the instruction type of the operation instruction when receiving the operation instruction sent by the user:

extracting ciphertext key data in the data packet to be loaded;

A4, the source code protection method according to A2, before the step of obtaining the instruction type of the operation instruction when receiving the operation instruction sent by the user, further includes:

The source code protection method according to A5 and A4, wherein the step of running the target software and monitoring a source code operation interface of the target software includes:

acquiring an installation path of the target software;

running the target software based on the installation path;

A6, the source code protection method according to A5, wherein the step of obtaining the installation path of the target software includes:

detecting whether the target software is installed;

and when the installation is completed, acquiring the installation path of the target software.

A7, the source code protection method according to A6, wherein the step of downloading the software installation package of the target software according to the download path and performing security verification on the software installation package includes:

A8, the source code protection method according to A5, further including, after the step of running the target software based on the installation path:

A9, the source code protection method according to A5, further including, after the step of running the target software based on the installation path:

A10, as in any one of the source code protection methods described in A1-A9, the step of performing encryption and packaging on the source code to be encrypted according to the encryption key information to obtain a ciphertext source code packet includes:

packaging the source code to be encrypted to obtain a source code resource package;

A11, as in any one of the source code protection methods described in A1 to A9, the step of generating ciphertext key data according to the encryption key information and adding the ciphertext key data to the ciphertext source code packet includes:

A12, as in any one of A1 to A9, the step of obtaining encryption key information corresponding to a source code to be encrypted includes:

The invention discloses a B13 source code protection device, which comprises the following modules:

B14, as for the source code protection apparatus described in B13, the information obtaining module is further configured to obtain an instruction type of the source code operation instruction when receiving the source code operation instruction sent by the user; if the instruction type is a source code packaging type, determining a source code access path according to the source code operation instruction; and reading the source code to be encrypted according to the source code access path.

B15, as the source code protection device described in B14, the source code processing module is further configured to search for a data packet to be loaded according to the source code operation instruction when the instruction type is a source code loading instruction; extracting ciphertext key data in the data packet to be loaded; decrypting the ciphertext key data through a preset module public key to obtain encryption key information; and decrypting the data packet to be loaded according to the decryption key information to obtain an application source code, and loading the application source code.

B16, as for the source code protection device described in B14, the information obtaining module is further configured to determine target software according to the software starting instruction when receiving the software starting instruction; running the target software and monitoring a source code operation interface of the target software; and when detecting that the source code operation interface is called, taking an instruction for calling the source code operation interface as a source code operation instruction.

B17, the source code protection device as described in B16, the information obtaining module is further configured to obtain an installation path of the target software; running the target software based on the installation path; and monitoring a source code operation interface of the target software when the target software is successfully operated.

B18, the source code protection device as described in B17, the information obtaining module is further configured to detect whether the target software is installed; if the target software is not installed, acquiring a downloading path of the target software; downloading the software installation package of the target software according to the downloading path, and carrying out security verification on the software installation package; when the security verification passes, installing the target software according to the software installation package; and when the installation is finished, acquiring the installation path of the target software.

The invention discloses C19 and source code protection equipment, which comprises: a processor, a memory, and a source code protection program stored on the memory and executable on the processor, the source code protection program when executed implementing the steps of the source code protection method as described above.

The invention discloses a D20 and a computer readable storage medium, wherein a source code protection program is stored on the computer readable storage medium, and the steps of the source code protection method are realized when the source code protection program is executed.

Claims

1. A source code protection method is characterized by comprising the following steps:

2. The source code protection method according to claim 1, wherein before the step of obtaining the encryption key information corresponding to the source code to be encrypted, the method further comprises:

3. The source code protection method according to claim 2, wherein after the step of obtaining the instruction type of the operation instruction when receiving the operation instruction sent by the user, the method further comprises:

extracting cipher key data in the data packet to be loaded;

4. The source code protection method according to claim 2, wherein before the step of obtaining the instruction type of the operation instruction when receiving the operation instruction sent by the user, the method further comprises:

5. The source code protection method of claim 4, wherein the step of running the target software and monitoring a source code operation interface of the target software comprises:

acquiring an installation path of the target software;

running the target software based on the installation path;

6. The source code protection method of claim 5, wherein the step of obtaining the installation path of the target software comprises:

detecting whether the target software is installed;

7. The source code protection method according to claim 6, wherein the step of downloading the software installation package of the target software according to the download path and performing security check on the software installation package comprises:

and when the standard verification data is consistent with the software verification data, judging that the safety verification is passed.

8. A source code protection device is characterized by comprising the following modules:

the source code processing module is used for encrypting and packaging the source code to be encrypted according to the encryption key information to obtain a ciphertext source code packet;

9. A source code protection device, characterized in that the source code protection device comprises: a processor, a memory, and a source code protection program stored on the memory and executable on the processor, the source code protection program when executed implementing the steps of the source code protection method as claimed in any one of claims 1-7.

10. A computer-readable storage medium, having stored thereon a source code protection program, which when executed performs the steps of the source code protection method of any one of claims 1-7.