ADB tool usage method, device and electronic device

Abstract

The embodiments of the present disclosure disclose a method, device and electronic device for using the adb tool. A specific implementation of the method includes: receiving ciphertext information transmitted by a communication connection terminal, wherein the ciphertext information is information generated by encrypting plaintext information input by a user into the communication connection terminal; configuring the target usage permission to be enabled by the adb tool based on the ciphertext information; sending the configuration information of the target usage permission to the operating system, so that the operating system determines whether the target usage permission meets the enabling requirements based on the configuration information, and in response to the target usage permission meeting the enabling requirements, enables the target usage permission. This implementation can improve the security of enabling the usage permission of the adb tool.

Description

Technical Field

[0001] Embodiments of the present disclosure relate to the field of computer technology, and more particularly to a method, device, and electronic device for using an adb tool. Background Art

[0002] In actual applications, a user may use an adb (Android Debug Bridge) tool installed on a mobile terminal to operate relevant data of the operating system of the mobile terminal.

[0003] In a related manner, without any verification, a user can access the relevant data of the operating system of the mobile terminal through the adb tool. At this time, the relevant data of the operating system of the mobile terminal may lack security. Summary of the invention

[0004] This disclosure section is provided to introduce concepts in a brief form, which will be described in detail in the detailed description section below. This disclosure section is not intended to identify key features or essential features of the claimed technical solution, nor is it intended to limit the scope of the claimed technical solution.

[0005] Embodiments of the present disclosure provide a method, an apparatus, and an electronic device for using an adb tool, which can improve the security of enabling the use permission of the adb tool.

[0006] In a first aspect, an embodiment of the present disclosure provides a method for using an adb tool, the method comprising: receiving ciphertext information transmitted by a communication connection terminal, wherein the ciphertext information is information generated by encrypting plaintext information input by a user into the communication connection terminal; configuring target usage permissions to be enabled by the adb tool based on the ciphertext information; sending configuration information of the target usage permissions to an operating system, so that the operating system determines whether the target usage permissions meet the enabling requirements based on the configuration information, and enabling the target usage permissions in response to the target usage permissions meeting the enabling requirements.

[0007] In a second aspect, an embodiment of the present disclosure provides an adb tool usage device, the device comprising: a receiving unit, for receiving ciphertext information transmitted by a communication connection terminal, wherein the ciphertext information is information generated by encrypting plaintext information input by a user to the communication connection terminal; a configuration unit, for configuring target usage permissions to be enabled by the adb tool based on the ciphertext information; a sending unit, for sending configuration information of the target usage permissions to an operating system, so that the operating system determines whether the target usage permissions meet the enabling requirements based on the configuration information, and enables the target usage permissions in response to the target usage permissions meeting the enabling requirements.

[0008] In a third aspect, an embodiment of the present disclosure provides an electronic device, comprising: one or more processors; a storage device for storing one or more programs, when the one or more programs are executed by the one or more processors, the one or more processors implement the adb tool usage method as described in the first aspect.

[0009] In a fourth aspect, an embodiment of the present disclosure provides a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method for using the adb tool as described in the first aspect.

[0010] The embodiments of the present disclosure provide adb tool usage method, device, and electronic device, wherein the communication connection terminal encrypts the plaintext information input by the user into ciphertext information, and transmits the ciphertext information to the mobile terminal. On the mobile terminal, the target usage permission to be enabled for the adb tool is configured based on the received ciphertext information. The operating system of the mobile terminal determines whether the target usage permission of the adb tool meets the enabling requirements based on the configuration information of the target usage permission, and enables the target usage permission of the adb tool on the premise that the target usage permission of the adb tool meets the enabling requirements. In this way, the security of enabling the usage permission of the adb tool can be improved, thereby ensuring the security of relevant data of the operating system of the mobile terminal. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the accompanying drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and the originals and elements are not necessarily drawn to scale.

[0012] Figure 1 is a flowchart of some embodiments of the method for using the adb tool disclosed in the present invention;

[0013] Figure 2 is a flowchart of configuring target usage permissions in some embodiments of the adb tool usage method disclosed herein;

[0014] Figure 3 is a flowchart of determining whether the target usage permission meets the opening requirement in some embodiments of the adb tool usage method disclosed in the present invention;

[0015] Figure 4 It is a schematic diagram of the structure of some embodiments of the adb tool using device disclosed in the present invention;

[0016] Figure 5 is an exemplary system architecture to which the adb tool usage method of the present disclosure may be applied in some embodiments;

[0017] Figure 6 is a schematic diagram of a basic structure of an electronic device provided according to some embodiments of the present disclosure. DETAILED DESCRIPTION

[0018] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments described herein, which are instead provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.

[0019] It should be understood that the various steps described in the method embodiments of the present disclosure may be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this respect.

[0020] The term "including" and its variations used herein are open inclusions, i.e., "including but not limited to". The term "based on" means "based at least in part on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". The relevant definitions of other terms will be given in the following description.

[0021] It should be noted that the concepts such as "first" and "second" mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0022] It should be noted that the modifications of "one" and "plurality" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".

[0023] The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are only used for illustrative purposes and are not used to limit the scope of these messages or information.

[0024] Please refer to Figure 1 , which shows the process of some embodiments of the method for using the adb tool according to the present disclosure. Figure 1 As shown, the method of using the adb tool includes the following steps:

[0025] Step 101, receiving ciphertext information transmitted by a communication connection terminal.

[0026] The communication connection terminal may be a terminal that establishes a communication connection with the mobile terminal.

[0027] The ciphertext information may be information generated by encrypting the plaintext information input by the user to the communication connection terminal. In practical applications, the plaintext information may be encrypted into ciphertext information by a variety of algorithms (eg, hash algorithms), which are not specifically limited here.

[0028] After receiving the plain text information input by the user, the communication connection terminal can obtain the cipher text information generated by encrypting the plain text information. Further, the communication connection terminal can send the cipher text information to the execution subject of the adb tool usage method, so that the execution subject can receive the cipher text information.

[0029] Step 102: Based on the ciphertext information, configure the target usage permissions of the adb tool to be enabled.

[0030] In actual applications, the adb tool often has multiple functions. The use permission of the adb tool may be the permission to use at least one function of the adb tool. The target use permission may be the permission to use the target function of the adb tool.

[0031] The execution subject may configure the target usage permission to be enabled by the adb tool based on the ciphertext information. In some scenarios, the execution subject may decode the ciphertext information into plaintext information. If the plaintext information obtained by decoding is correct, the execution subject may display prompt information for prompting the user to select the usage permission. Furthermore, the execution subject may configure the usage permission selected by the user as the target usage permission.

[0032] Step 103 : Send the configuration information of the target usage permission to the operating system, so that the operating system determines whether the target usage permission meets the opening requirement based on the configuration information, and opens the target usage permission in response to the target usage permission meeting the opening requirement.

[0033] The execution subject may send the configuration information of the target usage permission to the operating system of the mobile terminal. Further, the operating system of the mobile terminal may determine whether the target usage permission of the adb tool meets the opening requirement based on the configuration information. In response to the target usage permission of the adb tool meeting the opening requirement, the operating system of the mobile terminal may enable the usage permission of the adb tool.

[0034] In some scenarios, the execution subject may determine whether the time when the configuration information is received is within a preset opening time range. If the time when the configuration information is received is within the preset opening time range, the execution subject may determine that the target usage permission of the adb tool meets the opening requirements. If the time when the configuration information is received is not within the preset opening time range, the execution subject may determine that the target usage permission of the adb tool does not meet the opening requirements.

[0035] It can be understood that if the target usage permission of the adb tool is enabled, the target function of the adb tool can be used through the above-mentioned communication connection terminal, and then the relevant data of the above-mentioned operating system can be operated.

[0036] In this embodiment, the communication connection terminal encrypts the plaintext information input by the user into ciphertext information, and transmits the ciphertext information to the mobile terminal. On the mobile terminal, the target usage permission of the adb tool to be enabled is configured based on the received ciphertext information. The operating system of the mobile terminal determines whether the target usage permission of the adb tool meets the enabling requirements based on the configuration information of the target usage permission, and enables the target usage permission of the adb tool on the premise that the target usage permission of the adb tool meets the enabling requirements. In this way, the security of enabling the usage permission of the adb tool can be improved, thereby ensuring the security of the relevant data of the operating system of the mobile terminal.

[0037] In some embodiments, the plain text information is input by the user using a communication tool installed on the communication connection terminal. At this time, the user needs to use a specific communication tool to enable the target use permission of the adb tool.

[0038] In some embodiments, the plain text information includes at least one of the following: device information of the mobile terminal; contact information of the user; and permission information representing the usage permission applied for by the user.

[0039] The above-mentioned device information may be various information identifying the mobile terminal. For example, the device information may include the device number of the mobile terminal.

[0040] The contact information may be used to contact the user's various information. For example, the contact information may include the user's phone number, email address, etc.

[0041] In some embodiments, the plain text information includes device information of the mobile terminal. At this time, the communication connection terminal can obtain the cipher text information in the following manner.

[0042] Specifically, ciphertext information is generated by encrypting plaintext information locally.

[0043] It can be seen from this that the communication connection terminal can directly encrypt the plaintext information input by the user into ciphertext information locally.

[0044] In some embodiments, the plain text information includes the device information of the mobile terminal and the contact information of the user. At this time, the communication connection terminal can obtain the cipher text information in the following manner.

[0045] In the first step, plain text information is sent to the server, so that the server generates cipher text information by encrypting the plain text information, and feeds back the cipher text information to the user based on the contact information.

[0046] The second step is to receive the ciphertext information input by the user.

[0047] It can be seen that the server completes the encryption of plain text information into cipher text information and sends the cipher text information to the user. The communication connection terminal can obtain the cipher text information generated by the server without encrypting the plain text information locally. Thus, the workload of the communication connection terminal can be reduced.

[0048] In some embodiments, the execution subject can be Figure 2 The process shown configures the target usage permissions of the adb tool to be enabled. The process includes the following steps.

[0049] Step 201, obtaining plaintext information by decrypting ciphertext information.

[0050] The execution subject may decrypt the ciphertext information into plaintext information according to a decryption method corresponding to the encryption method of the plaintext information by the communication connection terminal.

[0051] Step 202: According to the hardware encryption status information and / or the permission information included in the plain text information, the target usage permission to be enabled by the adb tool is configured.

[0052] The hardware encryption status information may be information indicating whether the hardware of the mobile terminal is encrypted.

[0053] In some scenarios, if the hardware encryption status information indicates that the hardware of the mobile terminal is not encrypted, and the number of applications for the usage rights represented by the above permission information within a predetermined period of time is less than or equal to a preset number of times, the above execution entity may configure the usage rights represented by the above permission information as the target usage rights of the adb tool.

[0054] In these embodiments, the target usage permission to be enabled of the adb tool can be configured by comprehensively considering the hardware encryption status of the mobile terminal and the usage permission applied by the user. Thus, the security of enabling the usage permission of the adb tool can be further improved.

[0055] In some embodiments, the execution subject may configure the target usage permission to be enabled by the adb tool by executing at least one of step S1 and step S2.

[0056] Step S1, in response to the hardware encryption state information indicating that the hardware of the mobile terminal has been encrypted, configuring the usage permission indicated by the permission information as the target usage permission.

[0057] Step S2, in response to the hardware encryption state information indicating that the hardware of the mobile terminal is not encrypted, all usage permissions of the adb tool are configured as target usage permissions.

[0058] It is understandable that if the hardware of the mobile terminal is encrypted, the permission to use the adb tool applied by the user may be enabled. If the hardware of the mobile terminal is not encrypted, all permissions to use the adb tool may be enabled.

[0059] In some embodiments, the operating system of the mobile terminal can be Figure 3 The process shown in the figure determines whether the target usage permissions of the adb tool meet the requirements for enabling.

[0060] Step 301, obtaining plaintext information by decrypting the received ciphertext information.

[0061] The above operating system can decrypt the above ciphertext information into plaintext information according to the decryption method corresponding to the encryption method of the plaintext information by the communication connection terminal.

[0062] Step 302: Determine whether the target usage permission indicated by the configuration information is correctly configured according to the hardware encryption status information and / or the permission information included in the obtained plain text information.

[0063] The operating system may determine the target usage permission that should be configured based on the hardware encryption status information and / or the permission information included in the obtained plain text information. Further, the operating system may determine whether the target usage permission indicated by the configuration information is the target usage permission that should be configured. If yes, the operating system may determine that the target usage permission indicated by the configuration information is correctly configured. If not, the operating system may determine that the target usage permission indicated by the configuration information is incorrectly configured.

[0064] In some scenarios, the above operating system can be used as Figure 2 The manner of configuring the target usage permissions in the illustrated embodiment is similar to determining the target permissions that should be configured, and will not be described in detail here.

[0065] Step 303: In response to the target usage permission configuration indicated by the configuration information being correct, determining that the target usage permission meets the activation requirement.

[0066] Step 304: In response to the target usage permission configuration error indicated by the configuration information, determine that the target usage permission does not meet the opening requirement.

[0067] In actual applications, the configuration information of the target usage permission may be modified or tampered with. As a result, the target usage permission configured by the execution subject may be modified or tampered with. As a result, the usage permission of the adb tool may be opened incorrectly, which may further increase the risk of data leakage related to the operating system of the mobile terminal.

[0068] In these embodiments, after configuring the target usage permission of the adb tool, the operating system does not directly enable the target usage permission of the adb tool, but determines whether the target usage permission indicated by the configuration information is configured correctly, and enables the target usage permission of the adb tool on the premise that the target usage permission indicated by the configuration information is configured correctly. Thus, the risk of data leakage related to the operating system of the mobile terminal can be reduced.

[0069] In some embodiments, the above-mentioned execution entity may also execute at least one of step L1 and step L2.

[0070] Step L1, storing the ciphertext information locally in the mobile terminal, so as to reconfigure the target usage permission to be enabled by the adb tool based on the ciphertext information.

[0071] It can be understood that after the ciphertext information is stored locally in the mobile terminal, the target usage permission of the adb tool to be enabled can be configured directly based on the ciphertext information stored locally in the mobile terminal next time. At this time, the user does not need to re-enter the plaintext information on the communication connection terminal, and the communication connection terminal does not need to re-encrypt the plaintext information input by the user into ciphertext information and send it to the mobile terminal. In this way, the time for enabling the usage permission of the adb tool can be shortened.

[0072] Step L2, in response to receiving a clear instruction transmitted by the communication connection terminal, clear the ciphertext information.

[0073] The above-mentioned clearing instruction may be an instruction sent by the communication connection terminal under the instruction of the user, or may be an instruction actively sent by the communication connection terminal.

[0074] It can be understood that after enabling the target usage permission of the adb tool, clearing the ciphertext information can prevent the ciphertext information from being replaced. Thus, the security of enabling the usage permission of the adb tool can be increased to a certain extent. In addition, clearing the ciphertext information can release a portion of the storage space of the mobile terminal, thereby improving the utilization efficiency of the storage space of the mobile terminal.

[0075] In some embodiments, the above execution entity may perform the following steps.

[0076] The first step is to determine whether there is ciphertext information locally in the mobile terminal in response to the operating system being restarted.

[0077] In the second step, in response to the fact that no ciphertext information exists locally on the mobile terminal, all usage permissions of the adb tool are closed.

[0078] The local ciphertext information does not exist in the mobile terminal, which often means that the ciphertext information has been cleared. Therefore, it can be determined that the user does not need to enable the use permission of the adb tool at this time. It can be understood that under the premise that the local ciphertext information does not exist in the mobile terminal, closing all the use permissions of the adb tool can prevent the relevant data of the mobile terminal operating system from being abused.

[0079] Further references Figure 4 As an implementation of the methods shown in the above figures, the present disclosure provides some embodiments of an adb tool using device, the device embodiment is similar to Figure 1 Corresponding to the method embodiment shown, the device can be specifically applied to various electronic devices.

[0080] like Figure 4 As shown, the adb tool using device of this embodiment includes a receiving unit 401, a configuration unit 402, and a sending unit 403. The receiving unit 401 is used to receive ciphertext information transmitted by the communication connection terminal, wherein the ciphertext information is information generated by encrypting the plaintext information input by the user to the communication connection terminal; the configuration unit 402 is used to configure the target usage permission to be enabled by the adb tool based on the ciphertext information; the sending unit 403 is used to send the configuration information of the target usage permission to the operating system, so that the operating system determines whether the target usage permission meets the enabling requirements based on the configuration information, and enables the target usage permission in response to the target usage permission meeting the enabling requirements.

[0081] In this embodiment, the specific processing of the receiving unit 401, the configuration unit 402, and the sending unit 403 of the adb tool using device and the technical effects thereof can be referred to in Figure 1 The relevant descriptions of step 101, step 102, and step 103 in the corresponding embodiment are not repeated here.

[0082] In some embodiments, the plain text information includes at least one of the following: device information of the mobile terminal; contact information of the user; and permission information representing the usage permission applied for by the user.

[0083] In some embodiments, the plaintext information includes permission information representing the usage permissions applied for by the user; the configuration unit 402 is further used to obtain the plaintext information by decrypting the ciphertext information; and configure the target usage permissions to be enabled by the adb tool according to the hardware encryption status information and / or the permission information included in the plaintext information.

[0084] In some embodiments, the configuration unit 402 is further configured to, in response to the hardware encryption state information indicating that the hardware of the mobile terminal has been encrypted, configure the usage permission indicated by the permission information as the target usage permission.

[0085] In some embodiments, the configuration unit 402 is further configured to, in response to the hardware encryption state information indicating that the hardware of the mobile terminal is not encrypted, configure all usage permissions of the adb tool as target usage permissions.

[0086] In some embodiments, the plain text information is input by the user using a communication tool installed on the communication connection terminal.

[0087] In some embodiments, the plaintext information includes permission information characterizing the usage permissions applied for by the user; the operating system determines whether the target usage permissions meet the activation requirements in the following manner: by decrypting the received ciphertext information to obtain the plaintext information; based on the hardware encryption status information and / or the permission information included in the obtained plaintext information, determining whether the target usage permissions indicated by the configuration information are configured correctly; in response to the target usage permissions indicated by the configuration information being configured correctly, determining that the target usage permissions meet the activation requirements; in response to the target usage permissions indicated by the configuration information being incorrectly configured, determining that the target usage permissions do not meet the activation requirements.

[0088] In some embodiments, the adb tool using device further includes a storage unit (not shown in the figure) and / or a clearing unit (not shown in the figure). The storage unit is used to store the ciphertext information locally in the mobile terminal so as to reconfigure the target usage permission to be enabled by the adb tool based on the ciphertext information; the clearing unit is used to clear the ciphertext information in response to receiving a clearing instruction transmitted by the communication connection terminal.

[0089] In some embodiments, the adb tool using device further includes a closing unit (not shown in the figure). The closing unit is used to determine whether there is ciphertext information locally in the mobile terminal in response to the restart of the operating system; in response to the absence of ciphertext information locally in the mobile terminal, close all usage permissions of the adb tool.

[0090] In some embodiments, the plaintext information includes device information of the mobile terminal; the communication connection terminal obtains the ciphertext information in the following manner: by locally encrypting the plaintext information to generate the ciphertext information.

[0091] In some embodiments, the plaintext information includes the device information of the mobile terminal and the contact information of the user; the communication connection terminal obtains the ciphertext information in the following manner: sending the plaintext information to the server so that the server generates the ciphertext information by encrypting the plaintext information, and based on the contact information, feeding back the ciphertext information to the user; receiving the ciphertext information input by the user.

[0092] Further references Figure 5 , Figure 5 An exemplary system architecture is shown in which the adb tool use method according to some embodiments of the present disclosure can be applied.

[0093] like Figure 5 As shown, the system architecture may include a communication connection terminal 501 and a mobile terminal 502. The communication connection terminal 501 and the mobile terminal 502 may be connected to each other via a USB data cable, a network, Bluetooth, or the like.

[0094] The adb tool and the operating system are installed on the mobile terminal 502. In some scenarios, the mobile terminal 502 can receive ciphertext information transmitted by the communication connection terminal 501, wherein the ciphertext information is information generated by encrypting the plaintext information input by the user to the communication connection terminal 501. The mobile terminal 502 can configure the target usage permission to be enabled by the adb tool based on the ciphertext information, and send the configuration information of the target usage permission to the operating system, so that the operating system determines whether the target usage permission meets the enabling requirements based on the configuration information, and enables the target usage permission in response to the target usage permission meeting the enabling requirements.

[0095] In some scenarios, a communication tool is installed on the communication connection terminal 501. The user can use the communication tool to input plain text information on the communication connection terminal 501.

[0096] The terminal (e.g., the communication connection terminal 501 and / or the mobile terminal 502) can be hardware or software. When the terminal is hardware, it can be various electronic devices with a display screen and supporting information interaction, including but not limited to smart phones, tablet computers, laptop computers, and desktop computers. When the terminal is software, it can be installed in the electronic devices listed above, and can be implemented as multiple software or software modules, or as a single software or software module, which is not specifically limited here.

[0097] It should be noted that the adb tool use method provided in the embodiment of the present disclosure may be executed by the mobile terminal 502 , and accordingly, the adb tool use device may be provided in the mobile terminal 502 .

[0098] It should be understood that Figure 5 The number of communication connection terminals and mobile terminals in the embodiment is only for illustration. Any number of communication connection terminals and mobile terminals may be provided according to implementation requirements.

[0099] Reference below Figure 6 , which shows an electronic device suitable for implementing some embodiments of the present disclosure (e.g., Figure 5The terminal in some embodiments of the present disclosure may include but is not limited to mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 6 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure. Figure 6 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0100] like Figure 6 As shown, the electronic device may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage device 608 into a random access memory (RAM) 603. In RAM 603, various programs and data required for the operation of the electronic device are also stored. The processing device 601, ROM 602, and RAM 603 are connected to each other via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0101] Typically, the following devices may be connected to the I / O interface 605: input devices 606 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; output devices 607 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; storage devices 608 including, for example, a magnetic tape, a hard disk, etc.; and communication devices 609. The communication devices 609 may allow the electronic device to communicate with other devices wirelessly or by wire to exchange data. Although Figure 6 An electronic device having various devices is shown, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead. Figure 6 Each block shown in the figure may represent one device, or may represent multiple devices as required.

[0102] In particular, according to some embodiments of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, some embodiments of the present disclosure include a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program contains program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication device 609, or installed from the storage device 608, or installed from the ROM 602. When the computer program is executed by the processing device 601, the above-mentioned functions defined in the method of the embodiment of the present disclosure are executed.

[0103] It should be noted that the computer-readable medium described in some embodiments of the present disclosure may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In some embodiments of the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In some embodiments of the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, in which a computer-readable program code is carried. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The computer readable signal medium may also be any computer readable medium other than a computer readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0104] In some embodiments, the client and the server may communicate using any currently known or future developed network protocol such as HTTP (HyperText Transfer Protocol), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), as well as any currently known or future developed network.

[0105] The computer-readable medium may be included in the electronic device, or may exist independently without being installed in the electronic device. The computer-readable medium carries one or more programs. When the one or more programs are executed by the electronic device, the electronic device: receives ciphertext information transmitted by the communication connection terminal, wherein the ciphertext information is information generated by encrypting the plaintext information input by the user into the communication connection terminal; configures the target usage permission to be enabled by the adb tool based on the ciphertext information; sends the configuration information of the target usage permission to the operating system, so that the operating system determines whether the target usage permission meets the enabling requirements based on the configuration information, and enables the target usage permission in response to the target usage permission meeting the enabling requirements.

[0106] Computer program code for performing the operations of some embodiments of the present disclosure may be written in one or more programming languages ​​or a combination thereof, including but not limited to object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0107] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0108] The units described in some embodiments of the present disclosure may be implemented by software or hardware. The names of these units do not limit the units themselves in some cases. For example, the receiving unit may also be described as a unit that "receives ciphertext information transmitted by a communication connection terminal".

[0109] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0110] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0111] The above descriptions are only some preferred embodiments of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of disclosure involved in the embodiments of the present disclosure is not limited to the technical solutions formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above disclosed concept. For example, the above features are replaced with the technical features with similar functions disclosed in the present disclosure (but not limited to) to form a technical solution.

[0112] In addition, although each operation is described in a specific order, this should not be understood as requiring these operations to be performed in the specific order shown or in a sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although some specific implementation details are included in the above discussion, these should not be interpreted as limiting the scope of the present disclosure. Some features described in the context of a separate embodiment can also be implemented in a single embodiment in combination. On the contrary, the various features described in the context of a single embodiment can also be implemented in multiple embodiments individually or in any suitable sub-combination mode.

[0113] Although the subject matter has been described in language specific to structural features and / or methodological logical actions, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. On the contrary, the specific features and actions described above are merely example forms of implementing the claims.

Claims

1. A method for using an adb tool, characterized in that: Applied to mobile terminals, including: Receiving ciphertext information transmitted by a communication connection terminal, wherein the ciphertext information is information generated by encrypting plaintext information input by a user to the communication connection terminal; Based on the ciphertext information, configure the target usage permissions of the adb tool to be enabled; Sending configuration information of the target usage permission to an operating system, so that the operating system determines whether the target usage permission meets an opening requirement based on the configuration information, and in response to the target usage permission meeting the opening requirement, opens the target usage permission; The plain text information includes permission information representing the usage permission applied for by the user; and The operating system determines whether the target usage permission meets the opening requirement in the following manner: Obtain plaintext information by decrypting the received ciphertext information; Determining whether the target usage permission indicated by the configuration information is correctly configured according to the hardware encryption status information and / or the permission information included in the obtained plaintext information; In response to the target usage permission indicated by the configuration information being configured correctly, determining that the target usage permission meets the opening requirement; In response to a target usage permission configuration error indicated by the configuration information, determining that the target usage permission does not meet the opening requirement; The plain text information includes permission information representing the usage permission applied for by the user; and The configuring the target usage permission to be enabled by the adb tool based on the ciphertext information includes: Obtaining the plaintext information by decrypting the ciphertext information; According to the hardware encryption status information and / or the permission information included in the plaintext information, the target usage permission to be enabled by the adb tool is configured.

2. The method according to claim 1, characterized in that The plain text information includes at least one of the following: device information of the mobile terminal; contact information of the user; and permission information representing the usage permission applied for by the user.

3. The method according to claim 1, characterized in that The configuring the target usage permission to be enabled by the adb tool according to the hardware encryption state information and / or the permission information included in the plaintext information includes: In response to the hardware encryption state information indicating that the hardware of the mobile terminal has been encrypted, the usage permission indicated by the permission information is configured as the target usage permission.

4. The method according to claim 1, characterized in that: The configuring the target usage permission to be enabled by the adb tool according to the hardware encryption state information and / or the permission information included in the plaintext information includes: In response to the hardware encryption state information indicating that the hardware of the mobile terminal is not encrypted, all usage permissions of the adb tool are configured as the target usage permissions.

5. The method according to claim 1, characterized in that The plain text information is input by a user using a communication tool installed in the communication connection terminal.

6. The method according to claim 1, characterized in that The method further comprises at least one of the following: The ciphertext information is stored locally in the mobile terminal, so as to reconfigure the target usage permission to be enabled by the adb tool based on the ciphertext information; In response to receiving a clear instruction transmitted by the communication connection terminal, clearing the ciphertext information.

7. The method according to claim 1, characterized in that The method further comprises: In response to the operating system being restarted, determining whether the ciphertext information exists locally on the mobile terminal; In response to the ciphertext information not existing locally on the mobile terminal, all usage permissions of the adb tool are closed.

8. The method according to any one of claims 1 to 7, characterized in that: The plain text information includes device information of the mobile terminal; and The communication connection terminal obtains the ciphertext information in the following manner: The ciphertext information is generated by encrypting the plaintext information locally.

9. The method according to any one of claims 1 to 7, characterized in that: The plain text information includes the device information of the mobile terminal and the contact information of the user; and The communication connection terminal obtains the ciphertext information in the following manner: Sending the plaintext information to a server, so that the server generates the ciphertext information by encrypting the plaintext information, and feeds the ciphertext information back to the user based on the contact information; The ciphertext information input by the user is received.

10. An adb tool using device, characterized in that: Applied to mobile terminals, including: A receiving unit, configured to receive ciphertext information transmitted by a communication connection terminal, wherein the ciphertext information is information generated by encrypting plaintext information input by a user to the communication connection terminal; A configuration unit, configured to configure the target usage permission to be enabled by the adb tool based on the ciphertext information; a sending unit, configured to send the configuration information of the target usage permission to the operating system, so that the operating system determines whether the target usage permission meets the opening requirement based on the configuration information, and opens the target usage permission in response to the target usage permission meeting the opening requirement; The plain text information includes permission information representing the usage permission applied for by the user; and The operating system determines whether the target usage permission meets the opening requirement in the following manner: Obtain plaintext information by decrypting the received ciphertext information; Determining whether the target usage permission indicated by the configuration information is correctly configured according to the hardware encryption status information and / or the permission information included in the obtained plaintext information; In response to the target usage permission indicated by the configuration information being configured correctly, determining that the target usage permission meets the opening requirement; In response to a target usage permission configuration error indicated by the configuration information, determining that the target usage permission does not meet the opening requirement; The plain text information includes permission information representing the usage permission applied for by the user; and The configuration unit is specifically used to obtain the plaintext information by decrypting the ciphertext information; and configure the target usage permission to be enabled by the adb tool according to the hardware encryption status information and / or the permission information included in the plaintext information.

11. An electronic device, characterized in that: include: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 9.

12. A computer readable medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 9 is implemented.

Images