Debugging connection method, computer equipment and debugging system

By using ordinary and customized public keys to distinguish device types in the Android debugging bridge, the problem of insufficient security of Android device debugging connection is solved, high-security connection of customized devices and convenient connection of ordinary devices is achieved, and the Debugging efficiency and reliability.

CN118945660APending Publication Date: 2024-11-12SHANGHAI INNOVATECH INFORMATION TECH
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410967943.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-18
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

In the conventional debugging connection of Android debugging bridge (ADB), there is a security risk to the device, especially for specially customized equipment, it is difficult to effectively improve the security of its debugging connection and prevent unrelated personnel from performing dangerous operations.

Method used

By sending a normal public key and a customized public key to the device to be debugged, the debug connection method is determined based on the type of device. The customized device can only be connected through a customized public key, while the ordinary device is connected through a normal public key, combined with the customized public key stored in memory. and quantity identification to ensure the reliability and safety of customized equipment.

Benefits of technology

It improves the debug connection safety of customized equipment, reduces the possibility of dangerous operations by unrelated personnel, and at the same time realizes convenient debugging connections for ordinary equipment, improving the efficiency and reliability of debugging connections.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118945660A_ABST
    Figure CN118945660A_ABST
Patent Text Reader

Abstract

The embodiment of the invention provides a debugging connection method, computer equipment and a debugging system. The debugging connection method comprises the following steps: sending a common public key to a first device, wherein the common public key is used for verifying whether the first device is a customized device; under the condition that the first equipment is customized equipment, determining that debugging connection with the first equipment fails; sending a customized public key to the first device, wherein the customized public key is used for realizing connection with the first device; and under the condition that the first equipment is the common equipment, determining that debugging connection with the first equipment is successful. In the technical scheme, the debugging connection of the customized equipment can be realized only through the customized public key, and the debugging connection of the common equipment can be realized through the common public key, so that the debugging connection safety of the customized equipment can be improved, and the debugging connection reliability is improved. The possibility that irrelevant personnel carry out dangerous operation on the customized equipment through any computer equipment is reduced, and debugging connection of common equipment can be realized by using the same computer equipment, so that convenience of debugging connection is facilitated.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of intelligent device communication, and more specifically, to a debugging connection method, a computer device and a debugging system. Background Art

[0002] Android Debug Bridge (ADB) is a mechanism that allows developers to interact with Android devices. It uses ADB tools to manage device applications, files, hardware, etc. Through ADB debugging connection, developers can install and uninstall applications, transfer files, manage devices, perform remote debugging, performance analysis, and other operations on Android devices. ADB debugging connection is a very important and commonly used function in Android development. It provides developers with powerful device management and debugging capabilities, which helps improve development efficiency and quality.

[0003] In the ADB regular debugging connection, any computer with the ADB tool installed can operate the Android device, which poses certain security risks for some specially customized devices. In view of this, how to improve the debugging connection security of the device is a technical problem that needs to be solved urgently. Summary of the invention

[0004] The embodiments of the present application provide a debugging connection method, a computer device, and a debugging system, which can improve the debugging connection security of the device.

[0005] In a first aspect, a debugging connection method is provided, including: sending a common public key to a first device to be debugged, the common public key being used to verify whether the first device is a customized device; if the first device is a customized device, determining that the debugging connection with the first device fails; sending a customized public key to the first device, the customized public key being used to achieve connection with the first device; if the first device is an ordinary device, determining that the debugging connection with the first device is successful.

[0006] Through the technical solution of the embodiment of the present application, a debugging connection method that is compatible with customized devices and ordinary devices is provided. For customized devices, debugging connection can only be achieved through customized public keys, while ordinary devices can achieve debugging connection through ordinary public keys. This technical solution can not only improve the debugging connection security of customized devices and reduce the possibility of unrelated personnel performing dangerous operations on the customized devices through any computer device, but also use the same computer device to achieve debugging connection of ordinary devices, which is conducive to the convenience of debugging connection.

[0007] In some possible implementations, the source code of the customized device is different from that of the ordinary device.

[0008] In some possible implementations, a customized public key is stored in a memory of the customized device.

[0009] Through the technical solution of this implementation, the customized public key is stored in the memory of the customized device rather than in external storage, and can be read relatively quickly, thereby establishing a fast debugging connection.

[0010] In some possible implementations, the source code of the customized device has a quantity identifier of the customized public key.

[0011] Through the technical solution of this implementation, the comprehensive quantity identification and the customized public key stored in the memory can further ensure the reliability and security of the customized device debugging connection.

[0012] In some possible implementations, when the first device is a customized device, the first device is used to compare the received public key with the customized public key stored in the memory; when the received public key is the same as the stored customized public key, the first device is used to establish a debugging connection; when the received public key is different from the stored customized public key, the first device is not used to establish a debugging connection.

[0013] In some possible implementations, when the first device is a common device, the first device is used to establish a debugging connection based on a common public key.

[0014] In some possible implementations, the debugging connection method further includes: storing a serial number and attribute information of the first device in a storage unit, where the attribute information is used to characterize whether the first device is a customized device or a common device.

[0015] In some possible implementations, the debugging connection method also includes: obtaining the serial number of the second device to be debugged; querying in the storage unit according to the serial number of the second device; if the second device is a customized device, sending a customized public key to the second device; if the second device is an ordinary device, sending an ordinary public key to the second device; if the second device is not found, first sending an ordinary public key to the second device, and determining whether to send a customized public key based on the connection result.

[0016] Through the technical solution of the embodiment of the present application, by storing the relevant information of each device being debugged for the first time, in the subsequent connection process, the computer device can quickly send the corresponding public key to the device to be debugged, while ensuring security, it can also improve the efficiency of the debugging connection.

[0017] In some possible implementations, when the first device is a customized device, determining that the debugging connection with the first device has failed includes: running a debugging device query command; and determining that the debugging connection with the first device has failed based on the running result of the debugging device query command; and / or, when the first device is an ordinary device, determining that the debugging connection with the first device has succeeded includes: running a debugging device query command; and determining that the debugging connection with the first device has succeeded based on the running result of the debugging device query command.

[0018] In some possible implementations, before sending the common public key to the first device, the debugging connection method further includes: generating the common public key.

[0019] In some possible implementations, the debugging connection method is applied to an Android debugging bridge tool in a computer device, and the first device includes an Android device.

[0020] In a second aspect, a computer device is provided, comprising: a debugging tool module, wherein the debugging tool module is used to execute the debugging connection method in the first aspect or any possible implementation manner of the first aspect to achieve a debugging connection with a first device.

[0021] In some possible implementations, the debugging tool module includes an Android Debug Bridge tool.

[0022] In a third aspect, a computer device is provided, comprising: a processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute: the debugging connection method in the first aspect or any possible implementation manner of the first aspect.

[0023] In a fourth aspect, a debugging system is provided, comprising: a computer device and a first device to be debugged; the computer device is used to execute the debugging connection method in the first aspect or any possible implementation manner of the first aspect to establish a debugging connection with the first device. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figure 1 It is a schematic structural block diagram of a debugging connection system provided in an embodiment of the present application.

[0025] Figure 2 It is a schematic flow chart of a debugging connection method provided in an embodiment of the present application.

[0026] Figure 3 It is a schematic flowchart of another debugging connection method provided in an embodiment of the present application.

[0027] Figure 4 It is a schematic flowchart of another debugging connection method provided in an embodiment of the present application.

[0028] Figure 5 It is a schematic flowchart of another debugging connection method provided in an embodiment of the present application.

[0029] Figure 6 It is a schematic structural block diagram of a computer device provided in an embodiment of the present application.

[0030] Figure 7 It is a schematic structural block diagram of another computer device provided in an embodiment of the present application.

[0031] Figure 8 It is a schematic structural block diagram of a debugging system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0032] The technical solution in this application will be described below in conjunction with the accompanying drawings.

[0033] Figure 1 A schematic structural block diagram of a debugging connection system provided in an embodiment of the present application is shown.

[0034] like Figure 1 As shown, the debugging connection system includes: a computer 101 and a mobile terminal device 102. The mobile terminal device 102 includes but is not limited to a handheld terminal device of the type of a mobile phone, a tablet computer, a smart watch, etc.

[0035] The computer 101 may be configured with a debugging tool, such as an ADB tool, etc. Through the debugging tool, a debugging connection with the mobile terminal device 102 may be achieved. When the computer 101 is configured with an ADB tool, the mobile terminal device 102 may be configured with an Android system, that is, the mobile terminal device 102 is an Android device.

[0036] Alternatively, in some other examples, the computer 101 may be configured with other types of debugging tools, and the mobile terminal device 102 may be other types of operating systems. After the computer 101 establishes a corresponding debugging connection with the mobile terminal device 102, the mobile terminal device 102 may also be debugged.

[0037] In some implementations, a single computer 101 can debug multiple mobile terminal devices 102. As an example, in an ADB debugging connection, when computer A needs to debug device A, device A may pop up a prompt box, and after the user clicks "allow", computer A can debug device A. Similarly, computer A can also use this method to perform corresponding debugging operations on other devices.

[0038] In addition, a single mobile terminal device 102 can also accept debugging of multiple computers 101. That is, as long as the debugging tool is installed on the computer 101, the debugging connection to any mobile terminal device 102 can be realized.

[0039] In the above technical solution, the debugging security of the computer 101 for the mobile terminal device 102 is low. For some specially developed and customized devices, it is not desirable for other unrelated persons to connect to the device through debugging tools, install third-party applications on the device, and view the relevant information of the device. If the above debugging connection method is used, it is impossible to restrict other unrelated persons from connecting to the device and performing unknown and dangerous operations on the device.

[0040] In view of this, an embodiment of the present application provides a debugging method, which has high connection security for specially developed and customized equipment and can restrict unrelated personnel from making debugging connections to the specially developed and customized equipment.

[0041] Figure 2 A schematic flowchart of a debugging connection method 200 provided in an embodiment of the present application is shown.

[0042] like Figure 2 As shown, the debugging connection method 200 includes the following steps.

[0043] S210: Sending a common public key to a first device to be debugged, where the common public key is used to verify whether the first device is a customized device.

[0044] S220: If the first device is a customized device, determine that the debugging connection with the first device fails.

[0045] S230: Send a customized public key to the first device, where the customized public key is used to achieve connection with the first device.

[0046] S240: When the first device is a common device, determine that the debugging connection with the first device is successful.

[0047] Specifically, the debugging connection method 200 can be applied to a computer device, for example, Figure 1 The computer 101 shown in FIG. More specifically, the debugging connection method 200 can be applied to a debugging tool configured in a computer device, such as an ADB tool.

[0048] The first device is a device to be debugged. For example, the first device can be Figure 1 The mobile terminal device 102 shown in FIG. Optionally, the first device may be an Android device equipped with an Android operating system.

[0049] In the above step S210, the computer device may send a common public key to the first device, and the common public key may be a random public key generated by the computer device itself. As an example, after the ADB tool is installed on the computer device, when the ADB service is started for the first time, a pair of public keys and private keys will be generated locally, wherein the public key can be used as a common public key. Then, the computer device may execute an adb shell command, so that the computer device sends the common public key to the first device.

[0050] In step S220, when the first device is a customized device, the customized device cannot realize debugging connection with the computer device based on the ordinary public key. Specifically, the debugging connection mode of the customized device is different from that of the ordinary device. The customized device may have a built-in storage of a customized public key, and it may directly perform matching verification based on the stored customized public key and the received ordinary public key. However, since the customized public key is different from the ordinary public key, the customized device cannot realize debugging connection with the computer device.

[0051] In other words, in an embodiment of the present application, even if the first device receives the common public key for the first time, the first device will not store the common public key, but will directly implement connection authentication based on the stored customized public key.

[0052] In step S230, after the computer device fails to debug the connection with the first device through the ordinary public key, it can determine that the first device is a customized device. Therefore, the computer device can send a customized public key to the first device again, and the first device can achieve a debugging connection with the computer device based on the customized public key.

[0053] In step S240, after the computer device sends the common public key to the first device, if the first device is a common device, the first device may establish a debugging connection with the computer device based on the common public key.

[0054] Through the technical solution of the embodiment of the present application, a debugging connection method that is compatible with customized devices and ordinary devices is provided. For customized devices, debugging connection can only be achieved through customized public keys, while ordinary devices can achieve debugging connection through ordinary public keys. This technical solution can not only improve the debugging connection security of customized devices and reduce the possibility of unrelated personnel performing dangerous operations on the customized devices through any computer device, but also use the same computer device to achieve debugging connection of ordinary devices, which is conducive to the convenience of debugging connection.

[0055] In some embodiments of the present application, the source code of the customized device is different from that of the ordinary device, so that after receiving the public key, even if the public key is not stored in its memory, the customized device will not establish a debugging connection based on the received public key and further store the received public key.

[0056] In some embodiments of the present application, a customized public key is stored in the memory of the customized device. The customized public key is in the form of a string rather than a file, which can save storage space. Moreover, the customized public key is stored in the memory of the customized device rather than in external storage, and can also be read relatively quickly, thereby establishing a fast debugging connection.

[0057] Optionally, by modifying the source code, a custom device can save a custom public key in / data / misc / adb / adb_keys.

[0058] In some embodiments of the present application, the source code of the customized device has a quantity identifier of the customized public key. Optionally, when the quantity identifier is 1, it means that the customized device can only achieve debugging connection through 1 customized public key. At this time, the memory of the customized device can only store 1 customized public key. If multiple customized public keys are stored in the memory of the customized device, the customized device cannot achieve debugging connection with the computer device. Alternatively, the quantity identifier can also be a value other than 1, which corresponds to the number of customized public keys stored in the memory of the customized device. In this case, the customized device can achieve debugging connection with multiple computer devices with different customized public keys.

[0059] Through the technical solution of this implementation, the comprehensive quantity identification and the customized public key stored in the memory can further ensure the reliability and security of the customized device debugging connection.

[0060] Figure 3 A schematic flow chart of another debugging connection method 300 provided in an embodiment of the present application is shown. In this embodiment, the first device is a customized device.

[0061] like Figure 3 As shown, the computer device establishes a wired connection with the first device. As an example, the wired connection may be a Universal Serial Bus (USB) connection, a serial port connection, or the like.

[0062] After establishing a wired connection, the computer device first sends a common public key to the first device. If the first device is a customized device, after receiving the public key, the first device is used to compare the received public key with the customized public key stored in the memory to determine whether the received public key is the same as the customized public key in the memory. If the received public key is different from the stored customized public key, the first device is not used to establish a debugging connection with the computer device. At this time, the debugging connection between the computer device and the first device fails. Then, the computer device sends the customized public key to the first device. If the received public key is the same as the stored customized public key, the first device establishes a debugging connection with the computer device.

[0063] Optionally, in Figure 3In the illustrated embodiment, after the first device receives the common public key sent by the computer device, the first device may pop up a debugging authorization box to the user. If the user agrees to the authorization, the first device then determines whether the received public key is the same as the customized public key in the memory.

[0064] In this way, the first device can perform related operations of the debugging connection with the authorization of the user, which is beneficial to further improve the security of the debugging connection.

[0065] Figure 4 A schematic flowchart of another debugging connection method 400 provided in an embodiment of the present application is shown. In this embodiment, the first device is a common device.

[0066] like Figure 4 As shown, after the computer device and the first device establish a wired connection, the computer device first sends a common public key to the first device, and the first device determines whether the received common public key is stored in the memory. If so, the first device can directly debug the connection with the computer device. If not, the first device can store the common public key, and in the subsequent connection process, the connection with the computer device can be directly established based on the stored common public key.

[0067] Optionally, if the first device determines that the received common public key is not stored in the memory, the first device may pop up a debugging authorization box to the user, and if the user agrees to the authorization, the first device stores the common public key.

[0068] Figure 5 A schematic flow chart of another debugging connection method 500 provided in an embodiment of the present application is shown. In this embodiment, the first device is a customized device.

[0069] like Figure 5 As shown, in Figure 2 Based on the illustrated embodiment, the debugging connection method 500 may further include the following steps.

[0070] S510: Storing the serial number and attribute information of the first device in a storage unit.

[0071] S520: Obtain the serial number of the second device.

[0072] S530: Query the storage unit according to the serial number of the second device.

[0073] S540: If the second device is a customized device, send a customized public key to the second device.

[0074] S550: When the second device is a common device, send a common public key to the second device.

[0075] S560: If the second device is not found, first send a common public key to the second device, and determine whether to send a customized public key based on the connection result.

[0076] In an embodiment of the present application, after the computer device establishes an initial debugging connection with the first device, it can determine whether the first device is a customized device or a common device, and thus can store the information of the first device in its storage unit, which may include the memory or external memory of the computer device, and the information of the first device may include the serial number (SN) and attribute information of the first device, and the attribute information may be used to characterize whether the first device is a customized device or a common device.

[0077] As an example, the attribute information may be an identifier for identifying the first device as a customized device or a common device. As another example, the attribute information may include a sequence table of different attributes, for example, a serial number table of customized devices and a serial number table of common devices may be stored in the storage unit. In the case where the first device is a customized device, the serial number of the first device may be stored in the serial number table of the customized device. Similarly, in the case where the first device is a common device, the serial number of the first device may be stored in the serial number table of the common device.

[0078] In an embodiment of the present application, the computer device can store information about the device being debugged for the first time. In a subsequent connection process, if a second device to be debugged requires a debugging connection, then after the second device is connected to the computer device by wire, the computer device can first obtain the serial number of the second device, and query the storage unit based on the serial number of the second device, and determine whether the second device is a customized device or an ordinary device, or a device being debugged for the first time based on the query result.

[0079] In some embodiments, the user can query the serial number of the second device in the second device, and input a debugging command carrying the serial number of the second device to the computer device, so that the computer device obtains the serial number of the second device. Optionally, the user can input an adb-s XXXX shell debugging command to the computer device, where XXXX is the serial number of the second device. After receiving the debugging command, the computer device queries the serial number of the second device in the storage unit.

[0080] In the case where the second device is a customized device, the computer device may send a customized public key to the second device; in the case where the second device is an ordinary device, the computer device may send an ordinary public key to the second device; in the case where the second device is not found, the ordinary public key is first sent to the second device, and then the customized public key is sent according to the connection result. The process can be referred to above. Figures 2 to 4 The relevant description of the illustrated embodiment will not be repeated here.

[0081] Through the technical solution of the embodiment of the present application, by storing the relevant information of each device being debugged for the first time, in the subsequent connection process, the computer device can quickly send the corresponding public key to the device to be debugged, while ensuring security, it can also improve the efficiency of the debugging connection.

[0082] See above Figures 3 to 5 Optionally, before the computer device sends the common public key, the computer device generates a common public key. As an example, an ADB tool is configured on the computer device. When the ADB tool is started for the first time, a pair of private key and public key is generated, and the public key can be used as the common public key.

[0083] In addition, the debugging tool (such as ADB tool) configured on the computer device is a customized debugging tool, and its source code is different from that of the ordinary debugging tool. The debugging tool can not only send the ordinary public key, but also continue to send the customized public key after the ordinary public key connection fails. The customized public key can be pre-stored in the computer device. Optionally, the customized public key and the ordinary public key can be stored in different paths of the computer device so that the debugging tool can distinguish and read them.

[0084] Optionally, in the above Figures 2 to 5 In the illustrated embodiment, the computer device may execute a debugging device query command, and determine whether the debugging connection with the first device fails or succeeds according to the execution result of the debugging device query command.

[0085] As an example, when the ADB tool is configured in the computer device, the adb devices query command can be used to query the status of other devices connected to the current computer device. The result of the query command can display the SN of the connected device and the status of the device. When the status is displayed as offline, it means that the device debugging connection has failed. When the status is displayed as device, it means that the device debugging connection has been successful.

[0086] The embodiment of the present application also provides a computer device. Figure 6 A schematic structural block diagram of a computer device 600 provided in an embodiment of the present application is shown.

[0087] like Figure 6 As shown, the computer device 600 may include a debugging tool module 610, and the debugging tool module 610 may be used to execute the debugging connection method of any of the above embodiments to achieve a debugging connection with the first device.

[0088] Optionally, in some implementations, the debugging tool module includes an Android Debug Bridge tool, namely, an ADB tool.

[0089] Figure 7A schematic structural block diagram of another computer device 700 provided in an embodiment of the present application is shown.

[0090] like Figure 7 As shown, the computer device 700 includes a processor 710 and a memory 720, wherein the memory 720 is used to store computer programs, and the processor 710 is used to call and run the computer program stored in the memory 720 to execute: the debugging connection method of any of the above embodiments.

[0091] The present application also provides a computer-readable storage medium for storing a computer program, wherein the computer program can enable a computer to execute: the debugging connection method of any of the above embodiments.

[0092] The embodiment of the present application also provides a debugging system. Figure 8 A schematic structural block diagram of a debugging system 800 provided in an embodiment of the present application is shown.

[0093] like Figure 8 As shown, the debugging system 800 includes a computer device 810 and a first device 820 to be debugged, wherein the computer device 810 is used to execute the debugging connection method of any of the above embodiments to establish a debugging connection with the first device 820.

[0094] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and modules described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0095] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0096] It should be understood that the specific examples in this article are only intended to help those skilled in the art better understand the embodiments of the present application, rather than to limit the scope of the embodiments of the present application.

[0097] It should also be understood that in the various embodiments of the present application, the size of the serial number of each process does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0098] It should also be understood that the various implementation methods described in this specification can be implemented individually or in combination, and the embodiments of the present application are not limited to this.

[0099] Unless otherwise stated, all technical and scientific terms used in the embodiments of the present application are the same as the meanings generally understood by those skilled in the art of the technical field of the present application. The terms used in the present application are only for the purpose of describing specific embodiments and are not intended to limit the scope of the present application. The term "and / or" used in the present application includes any and all combinations of one or more related listed items. The singular forms of "a kind of", "above" and "the" used in the embodiments of the present application and the appended claims are also intended to include majority forms, unless the context clearly indicates other meanings. In addition, the terms "first", "second" etc. are only used for description purposes and cannot be understood as indicating or suggesting relative importance.

[0100] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only exemplary, and the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interface, device or unit, which can be electrical, mechanical or other forms.

[0101] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0102] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A debugging connection method, characterized in that: include: Sending a common public key to a first device to be debugged, where the common public key is used to verify whether the first device is a customized device; In the case where the first device is a customized device, determining that a debugging connection with the first device fails; Sending a customized public key to the first device, where the customized public key is used to achieve connection with the first device; In the case that the first device is a common device, it is determined that the debugging connection with the first device is successful.

2. The debugging connection method according to claim 1, characterized in that: The customized device has a different source code from the common device.

3. The debugging connection method according to claim 2, characterized in that: The customized public key is stored in the memory of the customized device.

4. The debugging connection method according to claim 2, characterized in that: The source code of the customized device has a quantity identifier of the customized public key.

5. The debugging connection method according to any one of claims 1 to 4, characterized in that: In the case where the first device is a customized device, the first device is used to compare the received public key with the customized public key stored in the memory; In case the received public key is the same as the stored customized public key, the first device is used to establish a debugging connection; In case the received public key is different from the stored custom public key, the first device is not used to establish a debug connection.

6. The debugging connection method according to any one of claims 1 to 4, characterized in that: In the case that the first device is a common device, the first device is used to establish a debugging connection based on the common public key.

7. The debugging connection method according to any one of claims 1 to 4, characterized in that: The debugging connection method also includes: The serial number and attribute information of the first device are stored in a storage unit, where the attribute information is used to characterize that the first device is the customized device or the common device.

8. The debugging connection method according to claim 7, characterized in that: The debugging connection method also includes: Obtain the serial number of the second device to be debugged; searching in the storage unit according to the serial number of the second device; In a case where the second device is the customized device, sending the customized public key to the second device; In the case where the second device is the common device, sending the common public key to the second device; In the case that the second device is not found, the common public key is first sent to the second device, and whether to send the customized public key is determined according to the connection result.

9. The debugging connection method according to any one of claims 1 to 4, characterized in that: The determining, when the first device is a customized device, that the debugging connection with the first device fails includes: Run the debug device query command; Determining, according to the running result of the debugging device query command, that the debugging connection with the first device fails; and / or, in the case where the first device is a common device, determining that the debugging connection with the first device succeeds, comprises: Run the debug device query command; According to the running result of the debugging device query command, it is determined that the debugging connection with the first device is successful.

10. The debugging connection method according to any one of claims 1 to 4, characterized in that: Before sending the common public key to the first device, the debugging connection method further includes: The common public key is generated.

11. The debugging connection method according to any one of claims 1 to 4, characterized in that: The debugging connection method is applied to an Android debugging bridge tool in a computer device, and the first device includes an Android device.

12. A computer device, characterized in that: include: A debugging tool module, wherein the debugging tool module is used to execute the debugging connection method according to any one of claims 1 to 11 to achieve a debugging connection with a first device.

13. The computer device according to claim 12, characterized in that The debugging tool module includes an Android debugging bridge tool.

14. A computer device, characterized in that: include: A processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute: the debugging connection method according to any one of claims 1 to 11.

15. A debugging system, characterized in that: include: Computer equipment and a first device to be debugged; The computer device is used to execute the debugging connection method according to any one of claims 1 to 11 to establish a debugging connection with the first device.