Interaction management method and apparatus, and device and storage medium
By receiving the private keys and certificates associated with the software distribution operation of the terminal device, the malware push risk when management credentials are stolen or the system is invaded, significantly improving system security and preventing Installation and execution of malware.
Patent Information
- Application Number
- PCT/CN2024/096509
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-31
- Filing Date
- 2024-05-30
- Publication Date
- 2024-12-05
AI Technical Summary
When the existing terminal management system is stolen or the management system is invaded, there is a risk that malware will push malware to terminal devices through the push software distribution platform, resulting in control risks.
By receiving target information associated with the software distribution operation of the terminal device, including private keys and software distribution certificates, the distribution software is signed and securely verified, ensuring the security of the software distribution operation and preventing malicious tampering.
It effectively avoids the potential risks in software distribution operations in the case of security vulnerabilities in the management background or servers being intruded, significantly improves the security of the system, and prevents the installation and execution of malware.
Smart Images

Figure CN2024096509_05122024_PF_FP_ABST
Abstract
Description
Interaction management method, device, equipment and storage medium
[0001] This application claims priority to the Chinese invention patent application entitled “Method, apparatus, device and storage medium for interaction management” and application number 2023106401442, filed on May 31, 2023, the entire contents of which are incorporated by reference into this application. Technical Field
[0002] Example embodiments of the present disclosure generally relate to the field of computers, and more particularly, to methods, apparatuses, devices, and computer-readable storage media for interaction management. Background Art
[0003] Terminal management systems have the ability to push software and execute commands to managed devices. If management credentials are stolen or the management system is compromised, these capabilities could be exploited to push malware to managed devices and execute commands to control more devices. Some software distribution platforms have the ability to push software to all devices, creating this risk of attack.
[0004] Summary of the Invention
[0005] In a first aspect of the present disclosure, a method for interactive management is provided. The method includes receiving, via a first device, target information associated with the security of a software distribution operation of a second device, the target information including at least one of the following: a private key issued for the second device; a software distribution certificate related to the software distribution operation for the second device; signing at least one piece of software to be distributed at the second device based on the target information; and sending the signed at least one piece of software to be distributed to the second device, so that the second device completes the software distribution operation.
[0006] In a second aspect of the present disclosure, a method for interactive management is provided. The method includes receiving, via a second device, at least one signed piece of software to be distributed from a first device, the at least one piece of software to be distributed being signed using target information associated with the security of a software distribution operation of the second device, the target information including at least one of the following: a private key issued for the second device; a software distribution certificate associated with the software distribution operation for the second device; performing a security verification on the at least one piece of software to be distributed; and completing the software distribution operation in response to a successful verification.
[0007] In a third aspect of the present disclosure, an apparatus for interactive management is provided. The apparatus includes a receiving module configured to receive target information associated with the security of a software distribution operation on a second device, the target information including at least one of the following: a private key issued for the second device; a software distribution certificate related to the software distribution operation on the second device; a signing module configured to sign at least one piece of software to be distributed on the second device based on the target information; and a sending module configured to send the signed at least one piece of software to be distributed to the second device, so that the second device completes the software distribution operation.
[0008] In a fourth aspect of the present disclosure, an apparatus for interactive management is provided. The apparatus includes a receiving module configured to receive at least one signed software to be distributed from a first device, the at least one software to be distributed being signed using target information associated with the security of a software distribution operation of the apparatus, the target information including at least one of the following: a private key issued for the apparatus; a software distribution certificate associated with the software distribution operation for the apparatus; a verification module configured to perform a security verification on the at least one software to be distributed; and an execution module configured to complete the software distribution operation in response to a successful verification.
[0009] In a fifth aspect of the present disclosure, an electronic device is provided. The device includes at least one processing unit; and at least one memory coupled to the at least one processing unit and storing commands for execution by the at least one processing unit. When executed by the at least one processing unit, the commands cause the device to perform the method described in the first or second aspect.
[0010] In a sixth aspect of the present disclosure, a computer-readable storage medium is provided, wherein a computer program is stored on the medium, and when the program is executed by a processor, the method described in the first aspect or the second aspect is implemented.
[0011] It should be understood that the contents described in the summary of the present invention are not intended to limit the key features or important features of the embodiments of the present disclosure, nor are they intended to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS
[0012] 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. In the accompanying drawings, the same or similar reference numerals represent the same or similar elements, wherein:
[0013] FIG1 shows a schematic diagram of an example environment in which embodiments of the present disclosure can be implemented;
[0014] FIG2 shows a schematic diagram of an interaction process of interaction management according to some embodiments of the present disclosure;
[0015] FIG3 shows a schematic diagram of an interaction process of interaction management according to some embodiments of the present disclosure;
[0016] FIG4 shows a schematic diagram of an interaction process of interaction management according to some embodiments of the present disclosure;
[0017] FIG5 shows a schematic diagram of an interaction process of interaction management according to some embodiments of the present disclosure;
[0018] FIG6 shows a flowchart of a process of interaction management according to some embodiments of the present disclosure;
[0019] FIG7 shows a flowchart of a process of interaction management according to some embodiments of the present disclosure;
[0020] FIG8 shows a block diagram of an apparatus for interaction management according to some embodiments of the present disclosure;
[0021] FIG9 shows a block diagram of an apparatus for interaction management according to some embodiments of the present disclosure; and
[0022] FIG10 shows a block diagram of an electronic device capable of implementing various embodiments of the present disclosure. DETAILED DESCRIPTION
[0023] The following describes embodiments of the present disclosure in more detail 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 limited to the embodiments described herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of protection of the present disclosure.
[0024] In the description of the embodiments of the present disclosure, the term "including" and similar terms should be understood as open inclusion, i.e., "including but not limited to". The term "based on" should be understood as "based at least in part on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The term "some embodiments" should be understood as "at least some embodiments". Other explicit and implicit definitions may be included below.
[0025] As mentioned above, if administrative credentials are stolen and / or the management system is compromised, there is a potential risk of malware attacks when software distribution platforms push software to end devices. Once installed and executed on the end device, this malware could be compromised.
[0026] The various embodiments described herein provide a solution for interactive management. A software distribution device can receive target information related to the security of software distribution operations on a terminal device. This target information may include a private key issued for the terminal device or a software distribution certificate related to the software distribution operations on the terminal device. The software distribution device signs at least one piece of software to be distributed based on this target information. The software distribution device sends the signed at least one piece of software to be distributed to the terminal device, enabling the terminal device to complete the distribution of the software, such as installing the software or executing related commands.
[0027] According to the embodiments of the present disclosure, by using public key or certificate signature verification technology to perform security verification on software distribution operations, potential risks in software distribution operations when there are security holes in the management background or the server is invaded can be avoided.
[0028] Sample Environment
[0029] First, reference is made to FIG1 , which schematically illustrates a diagram of an example environment 100 in which example implementations according to the present disclosure may be implemented.
[0030] As shown in FIG. 1 , an environment 100 may include a first device 110 and a plurality of second devices 120 - 1 , 120 - 2 , and 120 - 3 connected to the first device 110 .
[0031] The first device 110 is a device capable of performing software distribution operations. For example, the first device 110 may be a device capable of hosting a digital office platform, capable of performing functions including but not limited to integrated identity and rights management, remote access, office network access, terminal asset management, and office security capabilities.
[0032] Multiple second devices 120-1, 120-2, and 120-3 may be deployed on the terminal side and may use the functions provided by the first device 110. In the embodiment of the present application, the multiple second devices 120-1, 120-2, and 120-3 may also be collectively referred to as second devices 120. The example environment 100 also includes a second device manager 140, and the multiple second devices 120-1, 120-2, and 120-3 may be managed by the second device manager 140.
[0033] The second device 120 can be any type of mobile terminal, fixed terminal or portable terminal, including a mobile phone, a desktop computer, a laptop computer, a notebook computer, a netbook computer, a tablet computer, a media computer, a multimedia tablet, a personal communication system (PCS) device, a personal navigation device, a personal digital assistant (PDA), an audio / video player, a digital camera / camcorder, a positioning device, a television receiver, a radio broadcast receiver, an e-book device, a gaming device or any combination thereof, including accessories and peripherals of these devices or any combination thereof. In some embodiments, the second device 120 can also support any type of interface for the user (such as a "wearable" circuit, etc.).
[0034] In some embodiments, the first device 110 may push software to the plurality of second devices 120 - 1 , 120 - 2 , and 120 - 3 , so that the software is installed or corresponding commands are executed on the plurality of second devices 120 - 1 , 120 - 2 , and 120 - 3 .
[0035] In some embodiments, the manager 140 of the second device may connect with the first device 110 to grant the first device 110 permission to distribute or push software and / or related security verification information to the plurality of second devices 120-1, 120-2, and 120-3 managed by the manager 140 of the second device. In addition, in some embodiments, the manager 130 of the second device 120 may also provide the first device 110 with an indication of the software to be pushed to the plurality of second devices 120-1, 120-2, and 120-3.
[0036] In some embodiments, the example environment 100 further includes a third device 130. The third device 130 can be, for example, various types of computing systems / servers capable of providing computing capabilities, including but not limited to mainframes, edge computing nodes, computing devices in cloud environments, and the like. For example, the third device 130 can be connected to the first device 110, the second device 120, and the second device manager 140, respectively, to provide support for security verification during software distribution operations.
[0037] It should be understood that the structure and functionality of environment 100 are described for exemplary purposes only and do not imply any limitation on the scope of the present disclosure.
[0038] Example Process for Interaction Management
[0039] Figures 2 through 5 illustrate schematic diagrams of processes 200 through 500 for interaction management according to some embodiments of the present disclosure. Processes 200 through 500 may involve first device 110, second device 120, third device 130, and second device manager 140. For ease of discussion, process 200 will be described with reference to environment 100 of Figure 1.
[0040] As shown in Figures 2 to 5, the first device 110 may include a front-end client platform 110-1 and a back-end server 110-2. As an example, the front-end client platform 110-1 may be connected to the management party 140 of the second device to receive commands from the management party 140 of the second device. The back-end server 110-2 may be connected to the second device 120 to implement software distribution operations. These components / modules may be integrated into the first device 110 or implemented independently of each other. It should be understood that the first device 110 may also include other suitable units / modules, and the scope of the present disclosure is not limited in this respect.
[0041] FIG2 shows a schematic diagram of a process 200 for interaction management according to some embodiments of the present disclosure.
[0042] As shown in FIG2 , the third device 130 may generate a public-private key pair issued for the second device 120 and provide the private key (202) to the manager 140 of the second device. For example, the issued public-private key pair may be used for security verification of software distribution operations for the second device 120. In some other embodiments, the public-private key pair may also be generated by the manager 140 of the second device. The manager 140 of the second device stores the private key and provides the public key corresponding to the private key to the third device 130.
[0043] During the software distribution process, the manager 140 of the second device provides (204) the software to be distributed and the private key issued for the second device 120 to the first device 110. For example, the manager 140 of the second device provides the private key to the front-end client platform 110-1. The front-end client platform 110-1 uses the private key to sign (206) the software to be distributed to generate a software signature string, and then provides (208) the software to be distributed and the software signature string to the back-end server 110-2.
[0044] Alternatively or additionally, the action of signing the software to be distributed to generate a software signature string can also be performed by the backend server 110-2. For example, the front-end client platform 110-1 provides a private key to the backend server 110-2. After receiving the corresponding software package to be distributed, the backend server 110-2 can use the private key to sign the software to be distributed to generate a software signature string.
[0045] The second device 120 may obtain (210) a public key corresponding to the private key and issued for the second device 120 from the third device 130. After receiving (212) the software package to be distributed and the software signature string from the first device 110 (e.g., the backend server 110-2), the second device 120 performs a security verification (214) on the software signature string using the public key. If the verification is successful, the software distribution operation is completed, such as executing the software installation or corresponding instructions.
[0046] In some embodiments, the second device 120 may also obtain information from the third device 130 about whether its manager 140 has enabled software distribution public key signature verification. In some embodiments, obtaining and verifying security information may be performed each time the second device 120 is started.
[0047] In some embodiments, the manager 140 of the second device may disable the aforementioned security verification process for the software distribution operation. Figure 3 shows a schematic diagram of a process 300 for interactive management according to some embodiments of the present disclosure.
[0048] 3 , the third device 130 may generate a public-private key pair issued for the second device 120 and provide the private key ( 302 ) to the second device manager 140. For example, the issued public-private key pair may be used to disable security verification of software distribution operations of the second device 120.
[0049] The second device's manager 140 provides (304) the private key issued for the second device 120 and a shutdown command that verifies the security of the software distribution operation to the first device 110. For example, the second device's manager 140 provides the private key to the front-end client platform 110-1 and uses the private key to sign the shutdown command at the front-end client platform 110-1 (306) to generate a command signature string. The front-end client platform 110-1 provides (308) the shutdown command and the command signature string to the back-end server 110-2.
[0050] The backend server 110-2 can obtain the public key corresponding to the private key and issued for the second device 120 from the third device 130. After receiving the shutdown command and the command signature string from the front-end client platform 110-1, the backend server 110-2 uses the public key to perform a security verification on the command signature string (312). If the verification is successful, the backend server 110-2 determines that the shutdown command is trustworthy, and then the first device 110 provides the shutdown command and the command signature string (314) to the second device 120 through the backend server 110-2.
[0051] The second device 120 can obtain (316) a public key corresponding to the private key and issued to the second device 120 from the third device 130. The second device 120 uses the public key to verify the command signature string again. If the verification is successful, the second device 120 executes (318) a command to close the security verification of the software distribution operation.
[0052] Through this method, the terminal device can only complete the software distribution operation or close the security verification after successful verification. By using the public key for verification, even if there is a security vulnerability in the terminal device management, the risk of malicious tampering and attack during the software distribution operation can be avoided.
[0053] In some other embodiments, security verification for software distribution operations may also be implemented through security certificates. Figure 4 shows a schematic diagram of a process 400 for interaction management according to some embodiments of the present disclosure.
[0054] As shown in Figure 4, the third device 130 can serve as a certificate authority. For example, the third device 130 can issue a software distribution certificate related to software distribution operations of the second device 120 to the second device's manager 140. It should be understood that the software distribution certificate issued by the third device 130 to the second device's manager 140 can include identification information specific to the second device 120, so that the software distribution certificate is specific to the second device 120. The second device 120 can be pre-configured with the root certificate of the software distribution certificate.
[0055] The third device 130 provides (402) the software distribution certificate to the management party 140 of the second device. During the software distribution process, the management party 140 of the second device provides (404) the software to be distributed, the certificate chain, and the private key to the first device 110. For example, the management party 140 of the second device provides the software to be distributed, the certificate chain, and the private key to the front-end client platform 110-1, so that the front-end client platform 110-1 uses the certificate chain and the private key to sign the software to be distributed (406) to generate a software signing certificate chain, and then provides (408) the software to be distributed and the software signing certificate chain to the back-end server 110-2.
[0056] Alternatively or additionally, the action of signing the software to be distributed to generate a software signature certificate chain can also be performed by the backend server 110-2. For example, the front-end client platform 110-1 provides the private key and certificate chain to the backend server 110-2. After receiving the corresponding software package to be distributed, the backend server 110-2 can use the private key and certificate chain to sign the software to be distributed to generate (410) a software signature certificate chain.
[0057] After receiving (412) the software package to be distributed and the software signature certificate chain from the first device 110 (e.g., the backend server 110-2), the second device 120 performs a security verification (414) on the software signature certificate chain using the public key in the pre-configured root certificate. If the verification is successful, the software distribution operation is completed, such as executing the software installation or corresponding instructions.
[0058] In some embodiments, the manager 140 of the second device may disable the aforementioned security verification process for the software distribution operation. Figure 5 shows a schematic diagram of a process 500 for interactive management according to some embodiments of the present disclosure.
[0059] As shown in FIG. 5 , the third device 130 provides ( 502 ) a software distribution certificate to the manager 140 of the second device.
[0060] The management party 140 of the second device provides (504) the certificate chain of the software distribution certificate and the shutdown command for security verification of the software distribution operation to the first device 110. For example, the management party 140 of the second device provides the certificate chain to the front-end client platform 110-1 and uses the certificate chain at the front-end client platform 110-1 to sign (506) the shutdown command to generate a command signature certificate chain. The front-end client platform 110-1 provides (508) the shutdown command and the command signature certificate chain to the back-end server 110-2.
[0061] Backend server 110-2 may be pre-configured with a root certificate for the software distribution certificate. Backend server 110-2 may use the public key of the root certificate to perform a security verification on the command signature certificate chain (510). If the verification is successful, backend server 110-2 determines that the shutdown command is trustworthy, and then first device 110 provides the shutdown command and the command signature certificate chain to second device 120 via backend server 110-2 (512).
[0062] Similarly, the second device 120 verifies the command signature certificate chain using the public key in the pre-configured root certificate. If the verification is successful, the second device 120 executes (514) a shutdown command for the security verification of the software distribution operation.
[0063] By using public-private key pairs and / or security certificates to verify software distribution operations, the system's security is maximized. Even if there's a security vulnerability in the backend or the server is compromised, as long as the private key remains intact, software distribution operations will not be affected.
[0064] Example Process
[0065] 6 shows a flow chart of a process 600 of interaction management according to some embodiments of the present disclosure. In some embodiments, the process 600 may be implemented by the first device 110, for example.
[0066] In block 610, the first device 110 receives target information associated with security of a software distribution operation of the second device, including at least one of the following: a private key issued for the second device; and a software distribution certificate related to the software distribution operation for the second device.
[0067] In block 620 , the first device 110 signs at least one software to be distributed at the second device based on the target information.
[0068] In block 630 , the first device 110 sends the signed at least one software to be distributed to the second device, so that the second device completes the software distribution operation.
[0069] In some embodiments, the first device can obtain the at least one software to be distributed and the private key; generate a software signature string by signing the at least one software to be distributed using the private key; and send the at least one software to be distributed and the software signature string generated by signing the at least one software to be distributed using the private key to the second device.
[0070] In some embodiments, the first device can, in response to detecting a security-verified shutdown command for the software distribution operation, obtain a public key issued for the second device corresponding to the private key, wherein the security-verified shutdown command is signed by the private key; verify the signed shutdown command using the public key; and in response to successful verification, send the shutdown command and a command signature string generated by signing the security command using the private key to the second device.
[0071] In some embodiments, the private key issued for the second device is obtained from a manager of the second device or from a third device.
[0072] In some embodiments, the first device can obtain the at least one software to be distributed and the software distribution certificate; generate a software signing certificate chain by signing the at least one software to be distributed using the private key of the software distribution certificate; and send the software signing certificate chain and the signed at least one software to be distributed to the second device.
[0073] In some embodiments, the first device can, in response to detecting a security-verified shutdown command for the software distribution operation, wherein the security-verified shutdown command is signed by the private key of the software distribution certificate, obtain the software distribution certificate public key corresponding to the private key; use the software distribution certificate public key to verify the command signature certificate chain generated by signing the shutdown command using the private key of the software distribution certificate; and in response to successful verification, send the shutdown command and the command signature certificate chain to the second device.
[0074] 7 shows a flow chart of a process 700 for interaction management according to some embodiments of the present disclosure. In some embodiments, the process 700 may be implemented by the second device 120, for example.
[0075] In box 710, the second device 120 receives at least one signed software to be distributed from the first device, and the at least one software to be distributed is signed via target information associated with the security of the software distribution operation of the second device, and the target information includes at least one of the following: a private key issued for the second device; a software distribution certificate related to the software distribution operation for the second device.
[0076] In block 720 , the second device 120 performs a security check on the at least one software to be distributed.
[0077] In block 730 , if the second device 120 succeeds in verification, then in block 740 , the second device 120 completes the software distribution operation.
[0078] In some embodiments, the second device can obtain a public key corresponding to the private key and issued for the second device; and use the public key to verify the software signature string, which is generated by signing the at least one software to be distributed using the private key.
[0079] In some embodiments, the second device can, in response to receiving a shutdown command to turn off security verification for the software distribution operation, obtain a public key corresponding to the private key issued for the second device; use the public key to verify the command signature certificate chain, which is generated by signing the shutdown command using the private key; and execute the shutdown command in response to successful verification.
[0080] In some embodiments, the second device can obtain the public key of the software distribution certificate; and use the public key to verify the software signature string, where the software signature string is generated by signing the at least one software to be distributed using the private key of the software distribution certificate.
[0081] In some embodiments, the second device can obtain the public key of the software distribution certificate in response to receiving a shutdown command to turn off the security verification for the software distribution operation; use the public key to verify the command signature certificate chain, which is generated by signing the shutdown command using the private key of the software distribution certificate; and execute the shutdown command in response to successful verification.
[0082] The solution disclosed herein can significantly improve system security during software distribution operations.
[0083] Example devices and equipment
[0084] The embodiments of the present disclosure also provide corresponding devices for implementing the above methods or processes. Figure 8 shows a schematic structural block diagram of a device 800 for interaction management according to some embodiments of the present disclosure.
[0085] As shown in Figure 8, apparatus 800 may include a receiving module 810 configured to receive target information associated with the security of a software distribution operation on the second device, the target information including at least one of the following: a private key issued for the second device; a software distribution certificate related to the software distribution operation on the second device. Apparatus 800 may also include a signing module 820 configured to sign at least one piece of software to be distributed on the second device based on the target information. Apparatus 800 may also include a sending module 830 configured to send the signed at least one piece of software to be distributed to the second device, so that the second device completes the software distribution operation.
[0086] In some embodiments, the sending module 830 is further configured to obtain the at least one software to be distributed and the private key; generate a software signature string by signing the at least one software to be distributed using the private key; and send the at least one software to be distributed and the software signature string generated by signing the at least one software to be distributed using the private key to the second device.
[0087] In some embodiments, the device 800 is also configured to, in response to detecting a security-verified shutdown command for the software distribution operation, obtain a public key issued for the second device corresponding to the private key, wherein the security-verified shutdown command is signed by the private key; verify the signed shutdown command using the public key; and in response to successful verification, send the shutdown command and a command signature string generated by signing the security command using the private key to the second device.
[0088] In some embodiments, the private key issued for the second device is obtained from a manager of the second device or from a third device.
[0089] In some embodiments, the apparatus 800 is further configured to obtain the at least one software to be distributed and the software distribution certificate; generate a software signing certificate chain by signing the at least one software to be distributed using the private key of the software distribution certificate; and send the software signing certificate chain and the signed at least one software to be distributed to the second device.
[0090] In some embodiments, the device 800 is further configured to, in response to detecting a security-verified shutdown command for the software distribution operation, wherein the security-verified shutdown command is signed by the private key of the software distribution certificate, obtain the software distribution certificate public key corresponding to the private key; use the software distribution certificate public key to verify the command signature certificate chain generated by signing the shutdown command using the private key of the software distribution certificate; and in response to successful verification, send the shutdown command and the command signature certificate chain to the second device.
[0091] FIG9 shows a schematic structural block diagram of an apparatus 900 for interaction management according to some embodiments of the present disclosure.
[0092] As shown in Figure 9, apparatus 900 may include a receiving module 910 configured to receive at least one signed piece of software to be distributed from a first device. The at least one piece of software to be distributed is signed using target information associated with the security of the software distribution operation of the apparatus, the target information including at least one of the following: a private key issued for the apparatus; or a software distribution certificate associated with the software distribution operation for the apparatus. Apparatus 900 may also include a verification module 920 configured to perform a security verification on the at least one piece of software to be distributed. Apparatus 800 may also include an execution module 930 configured to complete the software distribution operation in response to a successful verification.
[0093] In some embodiments, the apparatus 900 is further configured to obtain a public key corresponding to the private key and issued for the second device; and use the public key to verify a software signature string, where the software signature string is generated by signing the at least one software to be distributed using the private key.
[0094] In some embodiments, the device 900 is also configured to, in response to receiving a shutdown command to turn off security verification for the software distribution operation, obtain a public key corresponding to the private key and issued for the second device; use the public key to verify the command signature certificate chain, which is generated by signing the shutdown command using the private key; and in response to successful verification, execute the shutdown command.
[0095] In some embodiments, the device 900 is further configured to obtain the public key of the software distribution certificate; and use the public key to verify the software signature string, where the software signature string is generated by signing the at least one software to be distributed using the private key of the software distribution certificate.
[0096] In some embodiments, the device 900 is also configured to obtain the public key of the software distribution certificate in response to receiving a close command to close the security verification for the software distribution operation; use the public key to verify the command signature certificate chain, which is generated by signing the close command using the private key of the software distribution certificate; and execute the close command in response to successful verification.
[0097] The units included in the device 800 and / or the device 900 can be implemented in various ways, including software, hardware, firmware or any combination thereof. In some embodiments, one or more units can be implemented using software and / or firmware, such as machine executable instructions stored on a storage medium. In addition to or as an alternative to machine executable instructions, some or all of the units in the device 800 and / or the device 900 can be implemented at least in part by one or more hardware logic components. As an example and not limitation, exemplary types of hardware logic components that can be used include field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), system on chip (SOCs), complex programmable logic devices (CPLDs), and the like.
[0098] Figure 10 shows a block diagram of an electronic device / server 1000 in which one or more embodiments of the present disclosure may be implemented. It should be understood that the electronic device / server 1000 shown in Figure 10 is merely exemplary and should not be construed as limiting the functionality and scope of the embodiments described herein.
[0099] As shown in FIG10 , electronic device / server 1000 is in the form of a general-purpose electronic device. Components of electronic device / server 1000 may include, but are not limited to, one or more processors or processing units 1010, memory 1020, storage device 1030, one or more communication units 1040, one or more input devices 1060, and one or more output devices 1060. Processing unit 1010 may be a real or virtual processor and is capable of performing various processes according to programs stored in memory 1020. In a multi-processor system, multiple processing units execute electronic machine executable instructions in parallel to increase the parallel processing capabilities of electronic device / server 1000.
[0100] The electronic device / server 1000 typically includes a plurality of computer storage media. Such media can be any available media accessible to the electronic device / server 1000, including but not limited to volatile and non-volatile media, removable and non-removable media. The memory 1020 can be a volatile memory (e.g., a register, a cache, a random access memory (RAM)), a non-volatile memory (e.g., a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. The storage device 1030 can be a removable or non-removable medium and can include a machine-readable medium, such as a flash drive, a disk, or any other medium that can be used to store information and / or data (e.g., training data for training) and can be accessed within the electronic device / server 1000.
[0101] The electronic device / server 1000 may further include additional removable / non-removable, volatile / non-volatile storage media. Although not shown in Figure 10, a disk drive for reading or writing from a removable, non-volatile disk (e.g., a "floppy disk") and an optical drive for reading or writing from a removable, non-volatile optical disk may be provided. In these cases, each drive may be connected to a bus (not shown) by one or more data media interfaces. The memory 1020 may include a computer program product 1025 having one or more program modules configured to perform various methods or actions of various embodiments of the present disclosure.
[0102] The communication unit 1040 enables communication with other electronic devices via a communication medium. Additionally, the functions of the components of the electronic device / server 1000 can be implemented as a single computing cluster or multiple computing machines that can communicate via a communication connection. Thus, the electronic device / server 1000 can operate in a networked environment using logical connections to one or more other servers, network personal computers (PCs), or other network nodes.
[0103] Input device 1050 may be one or more input devices, such as a mouse, keyboard, or trackball. Output device 1060 may be one or more output devices, such as a display, speaker, or printer. Electronic device / server 1000 may also communicate with one or more external devices (not shown) via communication unit 1040 as needed, such as storage devices, display devices, or the like, with one or more devices that allow a user to interact with electronic device / server 1000, or with any device that allows electronic device / server 1000 to communicate with one or more other electronic devices (e.g., a network card, a modem, etc.). Such communication may be performed via an input / output (I / O) interface (not shown).
[0104] According to an exemplary implementation of the present disclosure, a computer-readable storage medium is provided, on which one or more computer commands are stored, wherein the one or more computer commands are executed by a processor to implement the method described above.
[0105] Various aspects of the present disclosure are described herein with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products implemented according to the present disclosure. It should be understood that each block of the flowcharts and / or block diagrams, and combinations of blocks in the flowcharts and / or block diagrams, can be implemented by computer-readable program commands.
[0106] These computer-readable program commands can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine such that when these commands are executed by the processing unit of the computer or other programmable data processing device, a device is generated that implements the functions / actions specified in one or more blocks in the flowchart and / or block diagram. These computer-readable program commands can also be stored in a computer-readable storage medium, where these commands cause the computer, programmable data processing device, and / or other device to operate in a specific manner. Thus, the computer-readable medium storing the commands comprises an article of manufacture that includes commands for implementing various aspects of the functions / actions specified in one or more blocks in the flowchart and / or block diagram.
[0107] Computer-readable program commands may also be loaded onto a computer, other programmable interaction management apparatus, or other device, so that a series of operational steps are performed on the computer, other programmable interaction management apparatus, or other device to produce a computer-implemented process, thereby causing the commands executed on the computer, other programmable interaction management apparatus, or other device to implement the functions / actions specified in one or more boxes in the flowchart and / or block diagram.
[0108] The flow charts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the systems, methods and computer program products according to multiple implementations of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a part for a module, program segment or command, and a part for a module, program segment or command comprises one or more executable commands for realizing the logical function of the specification. In some alternative implementations, the functions marked in the box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous boxes 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 box in the block diagram and / or flow chart, and the combination of the boxes in the block diagram and / or flow chart can be realized by a special hardware-based system that performs the function or action of the specification, or can be realized by a combination of special hardware and computer commands.
[0109] While various implementations of the present disclosure have been described above, the foregoing description is intended to be illustrative, non-exhaustive, and not limited to the disclosed implementations. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described implementations. The terminology used herein is selected to best explain the principles of the implementations, their practical applications, or improvements to existing technologies, or to enable others skilled in the art to understand the implementations disclosed herein.
Claims
1. A method of interactive management, comprising: receiving, through the first device, target information associated with the security of the software distribution operation of the second device, the target information comprising at least one of the following: a private key issued for the second device; a software distribution certificate related to the software distribution operation for the second device; Signing at least one software to be distributed at the second device based on the target information; as well as The at least one signed software to be distributed is sent to the second device, so that the second device completes the software distribution operation.
2. The method according to claim 1, wherein sending the at least one signed software to be distributed comprises: Obtaining the at least one software to be distributed and the private key; Generate a software signature string by signing the at least one software to be distributed using the private key; as well as The at least one software to be distributed and a software signature string generated by signing the at least one software to be distributed using the private key are sent to the second device.
3. The method according to claim 1, further comprising: In response to detecting a shutdown command for security verification of the software distribution operation, obtaining a public key issued for the second device corresponding to the private key, wherein the shutdown command for security verification is signed by the private key; Verifying the signed close command using the public key; as well as In response to successful verification, the shutdown command and a command signature string generated by signing the security command using the private key are sent to the second device. 4 . The method according to claim 1 , wherein the private key issued for the second device is obtained from a manager of the second device or from a third device.
5. The method according to claim 1, further comprising: Obtaining the at least one software to be distributed and the software distribution certificate; Generate a software signing certificate chain by signing the at least one software to be distributed using the private key of the software distribution certificate; as well as The software signing certificate chain and the at least one signed software to be distributed are sent to the second device.
6. The method according to claim 1, further comprising: In response to detecting a shutdown command for a security check of the software distribution operation, wherein the shutdown command for the security check is signed by a private key of the software distribution certificate, obtaining a public key of the software distribution certificate corresponding to the private key; Using the software distribution certificate public key, verifying a command signature certificate chain generated by signing the shutdown command using the private key of the software distribution certificate; as well as In response to successful verification, the shutdown command and the command signature certificate chain are sent to the second device.
7. A method of interactive management, comprising: Receiving, through the second device, at least one signed software to be distributed from the first device, the at least one software to be distributed being signed via target information associated with the security of a software distribution operation of the second device, the target information comprising at least one of the following: a private key issued for the second device; a software distribution certificate related to the software distribution operation for the second device; Performing a security check on the at least one software to be distributed; as well as In response to the verification being successful, the software distribution operation is completed.
8. The method according to claim 7, further comprising: Obtaining a public key corresponding to the private key and issued to the second device; as well as The public key is used to verify a software signature string, where the software signature string is generated by signing the at least one software to be distributed using the private key.
9. The method according to claim 7, further comprising: In response to receiving a close command for closing the security check for the software distribution operation, obtaining a public key issued for the second device corresponding to the private key; Using the public key to verify a command signature certificate chain, where the command signature certificate chain is generated by signing the shutdown command using the private key; as well as In response to the verification being successful, the close command is executed.
10. The method according to claim 7, further comprising: Obtaining the public key of the software distribution certificate; as well as The software signature string is verified using the public key, where the software signature string is generated by signing the at least one software to be distributed using the private key of the software distribution certificate.
11. The method according to claim 7, further comprising: In response to receiving a close command for closing the security check for the software distribution operation, obtaining a public key of the software distribution certificate; Using the public key to verify a command signature certificate chain, the command signature certificate chain is generated by signing the shutdown command using the private key of the software distribution certificate; as well as In response to the verification being successful, the close command is executed.
12. An interactive management device, comprising: A receiving module, configured to receive target information associated with the security of the software distribution operation of the second device, the target information comprising at least one of the following: a private key issued for the second device; a software distribution certificate related to the software distribution operation for the second device; A signature module, configured to sign at least one software to be distributed at the second device based on the target information; as well as A sending module sends the at least one signed software to be distributed to the second device, so that the second device completes the software distribution operation.
13. An interactive management device, comprising: A receiving module configured to receive at least one signed software to be distributed from a first device, wherein the at least one software to be distributed is signed via target information associated with the security of the software distribution operation of the device, the target information comprising at least one of the following: a private key issued for the device; Software related to the software distribution operation for the device Document distribution certificate; A verification module, configured to perform security verification on the at least one software to be distributed; as well as The execution module is configured to complete the software distribution operation in response to successful verification.
14. An electronic device comprising: at least one processing unit; as well as At least one memory, the at least one memory being coupled to the at least one processing unit and storing commands for execution by the at least one processing unit, the commands, when executed by the at least one processing unit, causing the electronic device to execute a method according to any one of claims 1 to 6 or any one of claims 7 to 11.
15. A computer-readable storage medium having a computer program stored thereon, wherein when the program is executed by a processor, the method according to any one of claims 1 to 6 or any one of claims 7 to 11 is implemented.
Citation Information
Patent Citations
Methods for achieving secure software delivery and distribution
CN102271130A
Method of monitoring downloading quantity of applications and apparatus thereof
CN106936800A
Security processing method, device and system for application installation
CN110362990A
Application signature method and system, transaction terminal and service platform
CN114329358A
Data distribution method and device, equipment and storage medium
CN114764503A
