1. A processing method for debugging files is characterized by comprising the following steps:

acquiring a target file to be uploaded;

decrypting the signature file corresponding to the target file through a preset key so as to detect the type of the target file;

and when the target file is detected to be a debugging file, terminating uploading the target file.

2. The method according to claim 1, wherein the key includes a first key and a second key, wherein a signature file corresponding to a debug file is obtained by encrypting the first key, and a signature file corresponding to an application file is obtained by encrypting the second key, and the detecting the type of the target file includes:

when the first key can decrypt the signature file corresponding to the target file, determining the target file as a debugging file;

and when the second key can decrypt the signature file corresponding to the target file, determining that the target file is an application file.

3. The method of claim 1, wherein before decrypting the signature file corresponding to the target file with a predetermined key, the method further comprises:

identifying the type of the target file through the configured attribute tag in the target file;

and when the target file is identified as the debugging file, terminating uploading of the target file.

4. The method of claim 1, further comprising:

and when the target file is an application file, uploading the target file to a storage space for publishing the target file.

5. A processing method for debugging files is characterized by comprising the following steps:

running the debugging file;

responding to the operation of the debugging file, and acquiring a secret key in the operation environment of the debugging file;

decrypting the signature file corresponding to the debugging file through the secret key so as to detect whether the debugging file is leaked or not;

and when the debugging file is detected to be leaked, the running of the debugging file is terminated.

6. The method of claim 5, wherein the debug file comprises a debug file framework, and wherein prior to running the debug file, the method further comprises:

based on the debugging file framework, sending a request for downloading a debugging plug-in package corresponding to the debugging file framework to a background;

and loading the downloaded debugging plug-in package into the debugging file framework to run the debugging file.

7. The method of claim 6, wherein after sending a request to a backend to download a debug plug-in package corresponding to the debug file framework, the method further comprises:

detecting whether the IP address of the sending request is legal or not;

terminating the sending of the request when the IP address is illegal;

detecting whether the downloaded debugging plug-in package exists in the debugging file framework;

and deleting the debugging plug-in package when the debugging plug-in package exists in the debugging file framework.

8. The method of claim 5, wherein the terminating the execution of the debug file comprises:

cutting off the connection between the debugging file and an external network in the running process;

and deleting the log record generated in the running process of the debugging file.

9. A device for processing a debug file, the device comprising:

a first acquisition unit configured to acquire a target file to be uploaded;

a first decryption unit, configured to decrypt, by using a predetermined key, a signature file corresponding to the target file to detect a type of the target file;

the first termination unit is used for terminating uploading the target file when the target file is detected to be the debugging file.

10. A device for processing a debug file, the device comprising:

an execution unit configured to execute the debug file;

a second obtaining unit configured to obtain a key in a running environment of the debug file in response to running of the debug file;

the second decryption unit is used for decrypting the signature file corresponding to the debugging file through the secret key so as to detect whether the debugging file is leaked or not;

and the second termination unit is used for terminating the operation of the debugging file when detecting that the debugging file is leaked.

Background

The debugging file is a program file used for debugging code logic in the development process of the application program, the debugging file usually contains a lot of core information of the application program, and once the debugging file is revealed, great potential safety hazards exist. At present, in the prior art, leakage protection of a debug file is weak, and an application program developer generally ensures that a published file is an application file intended for a user rather than a debug file, so how to weaken the risk of leakage of the debug file is an urgent technical problem to be solved.

Disclosure of Invention

Embodiments of the present application provide a method and an apparatus for processing a debug file, a computer-readable medium, and an electronic device, so that a risk of the debug file being leaked can be weakened at least to a certain extent.

Other features and advantages of the present application will be apparent from the following detailed description, or may be learned by practice of the application.

According to an aspect of the embodiments of the present application, there is provided a method for processing a debug file, including: acquiring a target file to be uploaded; decrypting the signature file corresponding to the target file through a preset key so as to detect the type of the target file; and when the target file is detected to be a debugging file, terminating uploading the target file.

According to an aspect of the embodiments of the present application, there is provided a processing apparatus for debugging a file, the apparatus including: a first acquisition unit configured to acquire a target file to be uploaded; a first decryption unit, configured to decrypt, by using a predetermined key, a signature file corresponding to the target file to detect a type of the target file; the first termination unit is used for terminating uploading the target file when the target file is detected to be the debugging file.

In some embodiments of the present application, based on the foregoing scheme, the key includes a first key and a second key, where a signature file corresponding to a debug file is obtained by encrypting the first key, and a signature file corresponding to an application file is obtained by encrypting the second key; the device further comprises: the first detection unit is used for determining the target file as a debugging file when the first key can decrypt the signature file corresponding to the target file; and when the second key can decrypt the signature file corresponding to the target file, determining that the target file is an application file.

In some embodiments of the present application, based on the foregoing solution, the apparatus further includes: the identification unit is used for identifying the type of the target file through an attribute tag configured in the target file before decrypting a signature file corresponding to the target file through a preset key; the first termination unit is configured to: and when the target file is identified as the debugging file, terminating uploading of the target file.

In some embodiments of the present application, based on the foregoing solution, the apparatus further includes: an uploading unit, configured to upload the target file to a storage space for publishing the target file when the target file is an application file

In the technical solutions provided in some embodiments of the present application, the type of the target file is detected by decrypting the signature file corresponding to the target file with a predetermined key, and uploading of the target file detected as the type of the debug file can be terminated, so that a situation that the debug file leaks due to a mistake of a worker can be prevented, and further a risk that the debug file is leaked can be weakened.

According to an aspect of the embodiments of the present application, there is provided a method for processing a debug file, including: running the debugging file; in response to the running of the debug file; decrypting the signature file corresponding to the debugging file through the secret key so as to detect whether the debugging file is leaked or not; and when the debugging file is detected to be leaked, the running of the debugging file is terminated.

According to an aspect of the embodiments of the present application, there is provided a processing apparatus for debugging a file, the apparatus including: an execution unit configured to execute the debug file; a second obtaining unit configured to obtain a key in a running environment of the debug file in response to running of the debug file; the second decryption unit is used for decrypting the signature file corresponding to the debugging file through the secret key so as to detect whether the debugging file is leaked or not; and the second termination unit is used for terminating the operation of the debugging file when detecting that the debugging file is leaked.

In some embodiments of the present application, based on the foregoing solution, the debug file includes a debug file framework, and the apparatus further includes: a sending unit, configured to send, to a background, a request for downloading a debug plug-in package corresponding to the debug file framework, based on the debug file framework, before running the debug file; and the loading unit is used for loading the downloaded debugging plug-in package into the debugging file frame so as to run the debugging file.

In some embodiments of the present application, based on the foregoing solution, the apparatus further includes: a second detection unit, configured to detect whether an IP address of the request for sending is legal after sending a request for downloading a debug plug-in package corresponding to the debug file frame to a background; a third terminating unit configured to terminate the transmission of the request when the IP address is not legitimate; a third detecting unit, configured to detect whether the downloaded debug plug-in package already exists in the debug file framework; and the deleting unit is used for deleting the debugging plug-in package when the debugging plug-in package exists in the debugging file framework.

In some embodiments of the present application, based on the foregoing solution, the second termination unit is configured to: cutting off the connection between the debugging file and an external network in the running process; and deleting the log record generated in the running process of the debugging file.

In the technical solutions provided in some embodiments of the present application, when a debug file is run, the leaked debug file is detected by decrypting a signature file corresponding to the debug file with a key acquired in a running environment of the debug file, so that the running of the debug file can be terminated in time, core code logic of the debug file can be protected under the condition that the debug file is leaked, and further, the risk of the leak of the debug file can be weakened.

According to an aspect of the embodiments of the present application, there is provided a computer-readable medium on which a computer program is stored, the computer program, when executed by a processor, implementing the processing method of a debug file as described in the above embodiments.

According to an aspect of an embodiment of the present application, there is provided an electronic device including: one or more processors; a storage device, configured to store one or more programs, which when executed by the one or more processors, cause the one or more processors to implement the processing method of the debug file as described in the above embodiments.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application. It is obvious that the drawings in the following description are only some embodiments of the application, and that for a person skilled in the art, other drawings can be derived from them without inventive effort. In the drawings:

FIG. 1 shows a schematic diagram of an exemplary system architecture to which aspects of embodiments of the present application may be applied;

FIG. 2 shows a flow diagram of a method of processing a debug file according to one embodiment of the present application;

FIG. 3 illustrates a detailed flow diagram for detecting the target file type according to one embodiment of the present application;

FIG. 4 illustrates a flow diagram of a method prior to decrypting a signature file corresponding to the target file with a predetermined key according to one embodiment of the present application;

FIG. 5 shows a block diagram of a processing device for debugging a file according to an embodiment of the present application;

FIG. 6 shows a flow diagram of a method of processing a debug file according to one embodiment of the present application;

FIG. 7 illustrates a flowchart of a method before running the debug file, according to one embodiment of the present application;

FIG. 8 illustrates a flowchart of a method after sending a request to a backend to download a debug plug-in package corresponding to the debug file framework, according to one embodiment of the present application;

FIG. 9 is a diagram illustrating a scenario in which a debug plug-in package download request is sent to a backend according to an embodiment of the present application;

FIG. 10 illustrates a detailed flow diagram for terminating the execution of the debug file according to one embodiment of the present application;

FIG. 11 shows a block diagram of a processing device for debugging a file according to an embodiment of the present application;

FIG. 12 illustrates a schematic structural diagram of a computer system suitable for use in implementing the electronic device of an embodiment of the present application.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art.

Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the application. One skilled in the relevant art will recognize, however, that the subject matter of the present application can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and so forth. In other instances, well-known methods, devices, implementations, or operations have not been shown or described in detail to avoid obscuring aspects of the application.

The block diagrams shown in the figures are functional entities only and do not necessarily correspond to physically separate entities. I.e. these functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor means and/or microcontroller means.

The flow charts shown in the drawings are merely illustrative and do not necessarily include all of the contents and operations/steps, nor do they necessarily have to be performed in the order described. For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the actual execution sequence may be changed according to the actual situation.

Fig. 1 shows a schematic diagram of an exemplary system architecture to which the technical solution of the embodiments of the present application can be applied.

As shown in fig. 1, the system architecture may include a terminal device (e.g., one or more of a smartphone 101, a tablet computer 102, and a portable computer 103 shown in fig. 1, but may also be a desktop computer, etc.), a network 104, and a server 105. The network 104 serves as a medium for providing communication links between terminal devices and the server 105. Network 104 may include various connection types, such as wired communication links, wireless communication links, and so forth.

It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation. For example, server 105 may be a server cluster comprised of multiple servers, or the like.

It should be noted that the processing method for the debug file provided in the embodiment of the present application is generally executed by a terminal device (for example, the portable computer 103), and accordingly, the processing device for the debug file is generally disposed in the terminal device. However, in other embodiments of the present application, the server 105 may also have a similar function as the terminal device, so as to execute the processing method of the debug file provided by the embodiments of the present application.

It is noted that the terms first, second and the like in the description and claims of the present application and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the objects so used are interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in other sequences than those illustrated or described herein.

The implementation details of the technical solution of the embodiment of the present application will be described in detail below:

the present embodiment provides a processing method of a debug file, and referring to fig. 2, a flowchart of a processing method of a debug file according to an embodiment of the present application is shown, and the processing method of the debug file can be executed by a device having a calculation processing function, such as the terminal device shown in fig. 1, or the server shown in fig. 1. As shown in fig. 2, the processing method of the debug file at least includes steps 210 to 250.

The following will describe steps 210 to 250 shown in fig. 2 in detail:

in step 210, a target file to be uploaded is obtained.

In this application, the target file may include a debugging file, and may also include an application file. The debugging file is a file used by a program developer for debugging code logic in the program development process, and the debugging file comprises specific information of codes, such as debug package files; the application file refers to a file which is issued by a program developer to a user and used by the user, and the application file can realize an application function like a debugging file, but core code information in the application file is already covered after processing, such as a release package file.

In step 230, the signature file corresponding to the target file is decrypted by a predetermined key to detect the type of the target file.

In this application, the predetermined key may refer to a key generated by an application developer to encrypt the target file, where the predetermined key may be a symmetric key or an asymmetric key, and the asymmetric key includes a public key and a private key.

In one embodiment of the present application, an application developer may generate two keys, a first key and a second key. Specifically, after generating an application file and a corresponding debugging file, an application developer may encrypt the debugging file through a first key to obtain a signature file corresponding to the debugging file, and encrypt the application file through a second key to obtain a signature file corresponding to the application file.

After the target file to be uploaded is acquired, the type of the target file can be detected in a manner that a signature file corresponding to the target file is decrypted by a predetermined key (namely, a first key and a second key).

Further, the detecting the type of the target file may be implemented by a method as shown in fig. 3.

Referring to fig. 3, a detailed flowchart for detecting the type of the target file according to an embodiment of the present application is shown, which may specifically include steps 231 to 232:

step 231, when the first key can decrypt the signature file corresponding to the target file, determining that the target file is a debug file

Step 232, when the second key can decrypt the signature file corresponding to the target file, determining that the target file is an application file.

In step 250, when the target file is detected to be a debugging file, the uploading of the target file is terminated.

In the application, when the target file is detected to be the application file, the target file is uploaded to a storage space for releasing the target file.

In this embodiment, the type of the target file is detected by decrypting the signature file corresponding to the target file with the predetermined key, and uploading of the target file detected as the type of the debug file can be terminated, so that the occurrence of debugging file leakage caused by error of a worker can be prevented.

In an embodiment of the present application, before decrypting the signature file corresponding to the target file by using the predetermined key, the method shown in fig. 4 may also be implemented.

Referring to fig. 4, a flowchart of a method before decrypting a signature file corresponding to the target file by using a predetermined key according to an embodiment of the present application is shown, which may specifically include steps 221 to 222:

step 221, identifying the type of the object file through the attribute tag configured in the object file.

In this application, an application developer should be able to configure an attribute tag for identifying a type of a target file in a generated target file, that is, configure different attribute tags in an application file and a corresponding debug file.

Before decrypting the signature file corresponding to the target file through a predetermined key, the type of the target file can be identified through an attribute tag configured in the target file.

Step 222, when the target file is identified as the debugging file, terminating the uploading of the target file.

In this embodiment, the type of the target file is identified by the attribute tag configured in the target file, and the type of the target file is detected by decrypting the signature file corresponding to the target file by using the predetermined key, so that the monitoring of the type of the target file to be uploaded can be better strengthened, and the uploading of the target file is terminated when the type of the target file is a debug file, so that the risk of leakage of the debug file can be further weakened.

The embodiment also provides a processing device for a debug file, which can be used for executing the processing method for the debug file in the above embodiments of the present application. For details that are not disclosed in the embodiments of the apparatus of the present application, please refer to the embodiments of the method for processing the debug file described above in the present application.

FIG. 5 shows a block diagram of a processing device for debugging files according to an embodiment of the application.

Referring to fig. 5, a device 500 for processing a debug file according to an embodiment of the present application includes: a first acquisition unit 501, a first decryption unit 502 and a first termination unit 503.

The first obtaining unit 501 is configured to obtain a target file to be uploaded; a first decryption unit 502, configured to decrypt, by using a predetermined key, a signature file corresponding to the target file to detect a type of the target file; a first terminating unit 503, configured to terminate uploading the target file when it is detected that the target file is a debug file.

In some embodiments of the present application, based on the foregoing scheme, the key includes a first key and a second key, where a signature file corresponding to a debug file is obtained by encrypting the first key, and a signature file corresponding to an application file is obtained by encrypting the second key; the device further comprises: the first detection unit is used for determining the target file as a debugging file when the first key can decrypt the signature file corresponding to the target file; and when the second key can decrypt the signature file corresponding to the target file, determining that the target file is an application file.

In some embodiments of the present application, based on the foregoing solution, the apparatus further includes: the identification unit is used for identifying the type of the target file through an attribute tag configured in the target file before decrypting a signature file corresponding to the target file through a preset key; the first termination unit 501 is configured to: and when the target file is identified as the debugging file, terminating uploading of the target file.

In some embodiments of the present application, based on the foregoing solution, the apparatus further includes: and the uploading unit is used for uploading the target file to a storage space for releasing the target file when the target file is an application file.

In the technical solutions provided in some embodiments of the present application, the type of the target file is detected by decrypting the signature file corresponding to the target file with a predetermined key, and uploading of the target file detected as the type of the debug file can be terminated, so that a situation that the debug file leaks due to a mistake of a worker can be prevented, and further a risk that the debug file is leaked can be weakened.

The embodiment provides a processing method of a debugging file. Referring to fig. 6, a flowchart of a processing method of a debug file according to an embodiment of the present application is shown, and the processing method of the debug file may be performed by a device having a calculation processing function, such as the terminal device shown in fig. 1, or the server shown in fig. 1. As shown in fig. 6, the method for processing the debug file at least includes steps 620 to 680.

The following will describe steps 620 to 680 shown in fig. 6 in detail:

in step 620, the debug file is run.

In the present application, the purpose of running the debug file is to debug the code logic in the application, which is normally done by the application developer by running the debug file.

In one embodiment of the application, the debug file comprises a debug file framework, wherein the debug file framework does not contain specific core code information about the application program.

Before running the debug file, the method shown in FIG. 7 may also be implemented.

Referring to fig. 7, a flowchart of a method before running the debug file according to an embodiment of the present application is shown, which may specifically include steps 611 to 613:

step 611, based on the debug file framework, sending a request for downloading a debug plug-in package corresponding to the debug file framework to a background.

Step 613, loading the downloaded debugging plug-in package into the debugging file framework to run the debugging file.

In the application, an application developer can split a debugging file for debugging application program code logic into a debugging file frame and a corresponding debugging plug-in package, wherein the corresponding debugging plug-in package comprises specific core code information about an application program, the application developer can store the debugging plug-in package corresponding to the debugging file frame in a background, and when the debugging file needs to be run, a request for downloading the debugging plug-in package corresponding to the debugging file frame can be sent to the background based on the debugging file frame, and the downloaded debugging plug-in package is loaded into the debugging file frame so as to run the debugging file.

In a specific implementation of an embodiment, the debug file framework may refer to a framework of a debug package file that does not include real logic, and the debug plug-in package may refer to a debug plug-in package that includes real logic, where the framework of the debug package file has the capability of downloading the debug plug-in package and loading the debug plug-in package. The method may include installing a frame of the debug package file in a device for operating the debug package file, and downloading the debug plug-in package and loading the debug plug-in package into the frame of the debug package file to operate the debug package file when the debug package file is operated.

In an embodiment of the present application, after sending a request for downloading a debug plug-in package corresponding to the debug file framework to a background, the method shown in fig. 8 may be further implemented.

Referring to fig. 8, a flowchart of a method after sending a request for downloading a debug plug-in package corresponding to the debug file framework to a background according to an embodiment of the present application is shown, which may specifically include steps 6121 to 6124:

step 6121, detect whether the IP address of the sending request is legal.

Step 6122, when the IP address is illegal, the sending of the request is terminated.

Step 6123, detect whether the downloaded debug plug-in package already exists in the debug file framework.

Step 6124, when the debugging plug-in package exists in the debugging frame, deleting the debugging plug-in package.

In the application, the running of the debug file should be completed by an application developer, when the debug file is run, a corresponding debug plug-in package needs to be downloaded in the background according to a debug file frame, and when the debug plug-in package is downloaded, the possibility that the debug file is leaked can be evaluated by detecting whether an IP address sending a download request is legal or not. Specifically, a fixed IP address (for example, an IP address of an intranet) may be set as a legal address, and when it is detected that the IP address for sending the download request is different from the set fixed IP address, the IP address for sending the download request may be considered to be illegal, and it may be further determined that the debug file has a possibility of being leaked, and therefore, it is necessary to terminate sending of the download debug plug-in package request.

Referring to fig. 9, a schematic view of a scenario of sending a debugging plug-in package download request to a background is shown, and as shown in fig. 9, when a device 902 in an intranet sends a request for downloading a debugging plug-in package to a background server 901, the result is "request success". And when the device 903 in the external network sends a request for downloading the debug plug-in package to the background server 901, the result is "request failure".

In a specific implementation of an embodiment, the debug file framework may be a debug package file framework, and the debug plug-in package may be a debug plug-in package. When downloading a corresponding debug plug-in package in the background according to the debug package file frame, if the IP address sending the request for downloading the debug plug-in package is detected to belong to the intranet network environment, the debug plug-in package can be downloaded, and if the IP address sending the request for downloading the debug plug-in package is detected not to belong to the intranet network environment, the download of the debug plug-in package is terminated.

In addition, after step 6122 in the above embodiment, it may also be detected whether the downloaded debugging plug-in package already exists in the debugging file framework, and when the debugging plug-in package exists in the debugging framework, the debugging plug-in package is deleted. This has the advantage that it is possible to prevent the occurrence of a situation in which core code information in the debug plug-in package is leaked due to a part or all of the debug plug-in package having been downloaded before the transmission of the debug plug-in package download request is terminated.

In the above embodiment, on the one hand, the advantage of splitting the debug file into the debug file frame and the corresponding debug plug-in package is that even if the debug file frame is leaked, the debug plug-in package cannot be leaked, and further, the core code information of the debug file cannot be leaked. On the other hand, the advantage of whether the IP address for sending the downloading request of the debugging plug-in package is legal or not is that whether the debugging file frame in the debugging file is leaked or not can be detected, so that the risk of leakage of the debugging plug-in package in the debugging file can be reduced.

In step 640, in response to the execution of the debug file, a key is obtained in the execution environment of the debug file.

In step 660, the signature file corresponding to the debug file is decrypted through the key to detect whether the debug file is leaked.

In this application, the running environment of the debug file may refer to a hardware environment of a device running the debug file.

In the present application, on the one hand, the key in the present application refers to a key generated by an application developer to encrypt the debug file. On the other hand, the debugging environment is generally executed by an application developer. Therefore, under the condition that the debugging file is not leaked, an application developer can obtain a correct key in a hardware environment for running the debugging file, and then decryption of a signature file corresponding to the debugging file is completed. When the debug file is leaked, the correct key cannot be obtained in the hardware environment for operating the debug file, and therefore decryption of the signature file corresponding to the debug file cannot be completed.

In step 680, upon detecting that the debug file is compromised, the running of the debug file is terminated.

In an embodiment of the present application, the terminating the running of the debug file may be implemented by the steps shown in fig. 10.

Referring to fig. 10, a detailed flowchart illustrating termination of the operation of the debug file according to an embodiment of the present application may specifically include steps 681 to 682:

and 681, cutting off the connection between the debugging file and the external network in the operation process.

Step 682, deleting the log record generated in the operation process of the debugging file.

Specifically, the log record includes debugging information generated during the process of running the debugging file.

The embodiment also provides an apparatus embodiment of the present application, which may be used to execute the processing method of the debug file in the foregoing embodiment of the present application. For details that are not disclosed in the embodiments of the apparatus of the present application, please refer to the embodiments of the method for processing the debug file described above in the present application.

FIG. 11 shows a block diagram of a processing device for debugging a file according to an embodiment of the present application;

referring to fig. 11, a device 1100 for processing a debug file according to an embodiment of the present application includes: an execution unit 1101, a second acquisition unit 1102, a second decryption unit 1103, and a second termination unit 1104.

Wherein, the running unit 1101 is used for running the debugging file; a second obtaining unit 1102 configured to obtain a key in a running environment of the debug file in response to running of the debug file; a second decryption unit 1103, configured to decrypt, by using the key, a signature file corresponding to the debug file to detect whether the debug file is leaked; a second termination unit 1104, configured to terminate the running of the debug file when the debug file is detected to be leaked.

In some embodiments of the present application, based on the foregoing solution, the debug file includes a debug file framework, and the apparatus further includes: a sending unit, configured to send, to a background, a request for downloading a debug plug-in package corresponding to the debug file framework, based on the debug file framework, before running the debug file; and the loading unit is used for loading the downloaded debugging plug-in package into the debugging file frame so as to run the debugging file.

In some embodiments of the present application, based on the foregoing solution, the apparatus further includes: a second detection unit, configured to detect whether an IP address of the request for sending is legal after sending a request for downloading a debug plug-in package corresponding to the debug file frame to a background; a third terminating unit configured to terminate the transmission of the request when the IP address is not legitimate; a third detecting unit, configured to detect whether the downloaded debug plug-in package already exists in the debug file framework; and the deleting unit is used for deleting the debugging plug-in package when the debugging plug-in package exists in the debugging file framework.

In some embodiments of the present application, based on the foregoing solution, the second termination unit is configured to: cutting off the connection between the debugging file and an external network in the running process; and deleting the log record generated in the running process of the debugging file.

In the technical solutions provided in some embodiments of the present application, when a debug file is run, the leaked debug file is detected by decrypting a signature file corresponding to the debug file with a key acquired in a running environment of the debug file, so that the running of the debug file can be terminated in time, core code logic of the debug file can be protected under the condition that the debug file is leaked, and further, the risk of the leak of the debug file can be weakened.

FIG. 12 illustrates a schematic structural diagram of a computer system suitable for use in implementing the electronic device of an embodiment of the present application.

It should be noted that the computer system 1200 of the electronic device shown in fig. 12 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application.

As shown in fig. 12, the computer system 1200 includes a Central Processing Unit (CPU)1201, which can perform various appropriate actions and processes, such as performing the methods described in the above embodiments, according to a program stored in a Read-Only Memory (ROM) 1202 or a program loaded from a storage section 1208 into a Random Access Memory (RAM) 1203. In the RAM 1203, various programs and data necessary for system operation are also stored. The CPU 1201, ROM 1202, and RAM 1203 are connected to each other by a bus 1204. An Input/Output (I/O) interface 1205 is also connected to bus 1204.

The following components are connected to the I/O interface 1205: an input section 1206 including a keyboard, a mouse, and the like; an output section 1207 including a Display device such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and a speaker; a storage section 1208 including a hard disk and the like; and a communication section 1209 including a Network interface card such as a LAN (Local Area Network) card, a modem, or the like. The communication section 1209 performs communication processing via a network such as the internet. A driver 1210 is also connected to the I/O interface 1205 as needed. A removable medium 1211, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like, is mounted on the drive 1210 as necessary, so that a computer program read out therefrom is mounted into the storage section 1208 as necessary.

In particular, according to embodiments of the application, the processes described above with reference to the flow diagrams may be implemented as computer software programs. For example, embodiments of the present application include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 1209, and/or installed from the removable medium 1211. The computer program executes various functions defined in the system of the present application when executed by a Central Processing Unit (CPU) 1201.

It should be noted that the computer readable medium shown in the embodiments of the present application may be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a Read-Only Memory (ROM), an Erasable Programmable Read-Only Memory (EPROM), a flash Memory, an optical fiber, a portable Compact Disc Read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In this application, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. Each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units described in the embodiments of the present application may be implemented by software, or may be implemented by hardware, and the described units may also be disposed in a processor. Wherein the names of the elements do not in some way constitute a limitation on the elements themselves.

As another aspect, the present application also provides a computer-readable medium, which may be contained in the electronic device described in the above embodiments; or may exist separately without being assembled into the electronic device. The computer readable medium carries one or more programs which, when executed by an electronic device, cause the electronic device to implement the method described in the above embodiments.

It should be noted that although in the above detailed description several modules or units of the device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the application. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.

Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a touch terminal, or a network device, etc.) to execute the method according to the embodiments of the present application.

Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the embodiments disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains.

It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.