A cloud server remote management method and device

Abstract

This specification provides a method and apparatus for remote management of a cloud server. The method is applied to a cloud server created for a user on a cloud server side, whereby the user communicates with the cloud server through a cloud service system. The method includes: in response to a received remote management request from the user for the cloud server, generating an asymmetric key pair for encrypting and decrypting privacy information in a remote management command; storing and maintaining the key pair in a secure storage space on the cloud server, and sending the public key of the key pair to the user through the cloud service system; in response to a received remote management command encrypted with the public key from the user, decrypting the remote management command using the private key corresponding to the public key, and executing the decrypted remote management command to remotely manage the cloud server.

Description

Technical Field

[0001] The embodiments described in this specification relate to the field of cloud computing technology, and more specifically, the embodiments described in this specification relate to a method and apparatus for remote management of a cloud server. Background Technology

[0002] With the development of cloud computing technology, renting cloud servers from cloud service providers has gradually become one of the mainstream choices for enterprise users. Typically, after renting a cloud server from a cloud service provider, users can use the cloud service system to send commands to the cloud server to manage it. However, when users send commands containing private information to the cloud server through the cloud service system, there may be privacy and security concerns. Summary of the Invention

[0003] To overcome the problems existing in the related technologies, this specification provides the following methods and apparatus.

[0004] In a first aspect of the embodiments of this specification, a remote management method for a cloud server is provided, applied to a cloud server created for a user on a cloud server-side platform, wherein the user communicates with the cloud server through a cloud service system; the method includes:

[0005] In response to a remote management request sent by a user to the cloud server, an asymmetric key pair is generated for encrypting and decrypting privacy information in the remote management command;

[0006] The key pair is stored and maintained in the secure storage space on the cloud server, and the public key in the key pair is sent to the user through the cloud service system.

[0007] In response to a remote management command encrypted with the public key sent by the user, the system decrypts the remote management command using the private key corresponding to the public key and executes the decrypted remote management command to remotely manage the cloud server.

[0008] In a second aspect of the embodiments of this specification, a cloud server remote management device is provided, applied to a cloud server created for a user on a cloud server side, wherein the user communicates with the cloud server through a cloud service system; the device includes:

[0009] A key pair generation unit is used to generate an asymmetric key pair for encrypting and decrypting privacy information in remote management commands in response to a remote management request sent by a user to the cloud server.

[0010] A public key sending unit is used to store and maintain the key pair in a secure storage space on the cloud server, and to send the public key in the key pair to the user through the cloud service system.

[0011] The remote management unit is configured to respond to a remote management command sent by the user and encrypted with the public key, decrypt the remote management command using the private key corresponding to the public key, and execute the decrypted remote management command to remotely manage the cloud server.

[0012] In a third aspect of the embodiments of this specification, a storage medium is provided; the storage medium stores a computer program that, when executed, implements the steps of the method described above.

[0013] In a fourth aspect of the embodiments of this specification, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the method described above.

[0014] The embodiments described above in this specification have at least the following beneficial effects:

[0015] In the above technical solution, by maintaining an asymmetric encryption / decryption key pair on the cloud server, sending the public key to the user so that the user can use the public key to encrypt commands containing private content, and decrypting and executing the encrypted command using the private key corresponding to the public key, the cloud service provider cannot obtain the command content before encryption throughout the entire command transmission process. This ensures the security and trustworthiness of the cloud service provider's service and guarantees the user's data security and privacy. Attached Figure Description

[0016] To more clearly illustrate the technical solutions in the embodiments or prior art of this specification, the accompanying drawings used in the description of the embodiments or prior art will be briefly introduced below. Obviously, the drawings described below are merely some embodiments recorded in this specification, and those skilled in the art can obtain other drawings based on these drawings.

[0017] Figure 1 A schematic diagram of the architecture of a cloud server remote management method according to an embodiment of this specification is shown.

[0018] Figure 2 A flowchart illustrating a method for remote management of a cloud server according to an embodiment of this specification is shown schematically.

[0019] Figure 3 An interactive flowchart illustrating an embodiment of a cloud server remote management method according to this specification is shown schematically.

[0020] Figure 4 An interactive diagram illustrating an embodiment of a cloud server remote management method according to this specification is shown schematically.

[0021] Figure 5 A block diagram schematically illustrates a cloud server remote management device according to an embodiment of this specification;

[0022] Figure 6 This diagram schematically illustrates a hardware structure of a computer device in which an information retrieval method according to an embodiment of this specification is implemented.

[0023] In the accompanying drawings, the same or corresponding reference numerals indicate the same or corresponding parts. Detailed Implementation

[0024] The principles and spirit of this specification will now be described with reference to several exemplary embodiments. It should be understood that these embodiments are given merely to enable those skilled in the art to better understand and implement this specification, and are not intended to limit the scope of this specification in any way. Rather, these embodiments are provided to make this specification more thorough and complete, and to fully convey the scope of this specification to those skilled in the art.

[0025] Those skilled in the art will recognize that the embodiments described herein can be implemented as a system, apparatus, device, method, or computer program product. Therefore, this specification can be specifically implemented in the following forms: entirely hardware, entirely software (including firmware, resident software, microcode, etc.), or a combination of hardware and software.

[0026] First, let's introduce some relevant concepts that may be involved in the instruction manual:

[0027] OpenAPI: refers to the API interface of cloud services provided by cloud vendors to users, which is generally provided to users for calling via HTTP or HTTPS.

[0028] Cloud service gateway: This refers to the server provided by the cloud provider that is responsible for receiving OpenAPI requests from users. Generally, this server forwards requests to the management server of the corresponding product if the API requested belongs to a different product.

[0029] Cloud service system: refers to the system provided by cloud providers that actually processes users' OpenAPI requests.

[0030] Cloud server: refers to a physical or virtual computer provided by a cloud provider to users; the server can be used by users to run computer programs.

[0031] Operation and maintenance agent program: refers to a computer program used to receive and execute remote commands from users. It is generally developed and provided by cloud vendors and runs on cloud servers.

[0032] With the development of cloud computing technology, renting cloud servers from cloud service providers has gradually become one of the mainstream choices for enterprise users. Cloud service providers can offer automated operation and maintenance capabilities for cloud servers by providing corresponding cloud service API interfaces. Users can use the cloud service system to send commands to the cloud server to manage it. Specifically, they can call the cloud gateway's API interface to send commands with specified content to a designated cloud server, and the management server stores the command and notifies the cloud server to receive and execute it. Typically, a proxy service can be set up on the cloud server to handle communication with the user. The user manages the cloud server by calling the cloud service API interface of this proxy service.

[0033] Cloud service providers can typically guarantee the privacy and confidentiality of data on users' cloud servers, for example, by adopting strict access control, data encryption, network isolation, and compliance certification measures.

[0034] However, during the process of users sending commands to cloud servers through the cloud service system, the transmission and storage of command content goes through multiple stages, including the cloud service gateway, management server, management database, and user cloud server. The command content can be recorded or viewed at each stage. When the command content contains information that needs to be kept confidential, the user's information privacy and content security cannot be guaranteed.

[0035] To overcome the problems existing in the related technologies, this specification provides the following embodiments.

[0036] The scheme described in this specification will now be explained in detail with reference to the accompanying drawings.

[0037] Please see Figure 1 , Figure 1 This is a schematic diagram of the architecture of a cloud server remote management system provided in an exemplary embodiment. For example... Figure 1 As shown, the system may include a network 10, a server 11, and several electronic devices, such as computers 12, 13, and 14.

[0038] Server 11 can be a physical server containing a single host, or it can be a virtual server, cloud server, etc., hosted in a host cluster. Computers 12-14 are just one type of electronic device that users can use. In reality, users can obviously also use electronic devices such as tablets, mobile phones, PDAs (Personal Digital Assistants), wearable devices (such as smart glasses, smartwatches, etc.), etc., and this specification does not limit this to one or at least one embodiment. Network 10 can include various types of wired or wireless networks.

[0039] In one embodiment, server 11 can cooperate with computers 12-14; wherein, computers 12-14 can receive user operations and upload the received commands and files to server 11 via network 10, and then server 11 processes the files based on the scheme described in this specification. In another embodiment, computers 12-14 can independently implement the scheme described in this specification; wherein, computers 12-14 receive user operations and process the received commands and files based on the scheme described in this specification to achieve remote management of the cloud server.

[0040] Please see Figure 2 , Figure 2 This is a flowchart illustrating a remote management method for a cloud server, provided in an exemplary embodiment. The method is applied to a processing device, which can be... Figure 1 The server 11 or computers 12-14 shown are examples of this.

[0041] The method may include the following steps:

[0042] Step 202: In response to the received remote management request for the cloud server sent by the user, generate an asymmetric key pair for encrypting and decrypting privacy information in the remote management command.

[0043] When a user rents a cloud server created for them on a cloud server provided by a cloud service provider, the user communicates with the cloud server through the cloud service system and sends remote management commands to manage the cloud server.

[0044] When remote management commands contain sensitive information that needs to be kept confidential, such as passwords or confidential data, transmitting these commands directly through a cloud service system may pose privacy and security risks.

[0045] It's possible to encrypt private information in remote commands before sending them to a cloud server. However, the decryption key is also private information and cannot be sent directly.

[0046] To solve this problem, asymmetric encryption methods can be used to encrypt private information in remote management commands. In this method, the public key used for encryption can be transmitted in plaintext, while the key used for decryption is only used on the cloud server side.

[0047] Therefore, asymmetric key pairs should be generated and maintained on a cloud server.

[0048] When a user needs to send a remote management command containing privacy information to the cloud server, they can send a remote management request instead of sending the remote management command directly.

[0049] After receiving the remote management request through the cloud service system, the cloud server can generate an asymmetric key pair corresponding to the request. This asymmetric key pair contains a public key and a private key; the public key is used to encrypt the private information in the remote management command, and the private key is used to decrypt the private information in the remote management command.

[0050] Step 204: Store and maintain the key pair in the secure storage space on the cloud server, and send the public key of the key pair to the user through the cloud service system.

[0051] After generating the asymmetric key pair, it can be stored and maintained in a secure storage space on a cloud server. The private key in the key pair is used for decryption; if the private key is leaked, the security of private information cannot be guaranteed.

[0052] The public key in the key pair is used only for encryption and can be transmitted in plaintext. The public key can be returned to the user as a response to the aforementioned remote management request via the cloud service system, allowing the user to use the public key to encrypt remote management commands.

[0053] Once the user receives the public key returned by the cloud server, they can use it to encrypt private content in remote management commands. Remote management commands encrypted with this public key can only be decrypted using the corresponding private key. Therefore, the user can send these encrypted remote management commands to the cloud server through the cloud service system.

[0054] Although the encrypted remote management command can be obtained at each stage of its transmission and storage, it cannot be decrypted because the corresponding private key is not available. Therefore, the transmission process is secure.

[0055] Step 206: In response to the remote management command encrypted with the public key sent by the user, the remote management command is decrypted using the private key corresponding to the public key, and the decrypted remote management command is executed to remotely manage the cloud server.

[0056] When the cloud server receives the remote management command encrypted with the public key from user Da Song, it can use the private key corresponding to the public key to decrypt the encrypted private content in the remote management command and obtain the decrypted remote management command.

[0057] After obtaining the decrypted remote management command, you can use it to remotely manage the cloud server. Once the remote command is executed, you can also send the execution result to the user.

[0058] The above embodiment maintains an asymmetric encryption / decryption key pair on a cloud server, sends the public key to the user so that the user can use the public key to encrypt commands containing private content, and after receiving the encrypted command, decrypts it using the private key corresponding to the public key and executes it. In the entire process of command transmission, the cloud service provider cannot obtain the command content before encryption, thereby ensuring the security and trustworthiness of the cloud service provider's service and ensuring the data security and privacy of the user.

[0059] Please see Figure 3 , Figure 3 An interactive flowchart illustrating an embodiment of a cloud server remote management method according to this specification is shown schematically.

[0060] The following combination Figure 3 This document describes the overall process of remote management of cloud servers.

[0061] like Figure 3 As shown in the manual, the remote management method for cloud servers mainly involves three entities: user 31, cloud service system 32, and cloud server 33. All communication between the user and the cloud server goes through the cloud service system; therefore, the cloud service system can be considered to have access to all content during the communication process between the user and the cloud server.

[0062] This remote management method can be broken down into the following steps:

[0063] 301. The user sends a remote management request to the cloud server;

[0064] 302. Generate a key pair on the cloud server;

[0065] 303. The cloud server sends a public key to the user;

[0066] 304. Users encrypt remote management commands using a public key;

[0067] 305. The user sends a remote management command encrypted with a public key to the cloud server;

[0068] 306. The cloud server uses the private key corresponding to the public key to decrypt remote management commands;

[0069] 307. The cloud server executes remote management commands.

[0070] like Figure 3 As shown, in the above steps, the information that the cloud service system can obtain includes: the remote management request obtained in step 301, the public key obtained in step 303, and the remote management request encrypted with the public key obtained in step 305. However, the private content in the remote management request cannot be obtained through the remote management request, the public key, and the remote management request encrypted with the public key.

[0071] In one illustrative embodiment shown in this specification, the remote management request sent by the user may also include key generation parameters, and the cloud server can generate an asymmetric key based on the aforementioned key management parameters.

[0072] Key generation parameters may include:

[0073] Key algorithm: Indicates the algorithm used to generate asymmetric key pairs, such as RSA (Rivest-Shamir-Adleman) algorithm, Elliptic Curve Cryptography (ECC) algorithm, DSA (Digital Signature Algorithm) algorithm, or ECDSA (Elliptic Curve Digital Signature Algorithm) algorithm, etc.

[0074] Key length: Indicates the length of the public key in the generated asymmetric key pair, such as 1024 bits, 2048 bits, etc. The length of the public key is generally related to the length of the plaintext to be encrypted, the encryption / decryption time, and the difficulty of cracking the encryption. Typically, the longer the plaintext to be encrypted, the larger the minimum key length required; the longer the key length, the longer the encryption / decryption time, and the greater the difficulty of cracking the encryption. Users can choose an appropriate key length according to their needs.

[0075] Key validity period: Indicates the duration for which the key is valid. Decryption can only be performed within the valid period; otherwise, the key becomes invalid. The key validity period can be set according to the duration required for encryption and communication. For example, the key validity period can be set to 60 seconds, 120 seconds, 300 seconds, etc.

[0076] Key Usage Count: Indicates the maximum number of times the key can be used. The key becomes invalid after this limit is exceeded. For example, it can be set to 1 time, 2 times, etc.

[0077] This manual does not specify the exact settings and format of the key generation parameters.

[0078] For example, the key generation parameters for a remote management request can be represented as follows:

[0079] --algorithm=rsa--time-to-live=60--max-access-times=1;

[0080] The above key generation parameters indicate that the key pair to be generated is an asymmetric key pair with an RSA algorithm, an effective duration of 60 seconds, and a maximum number of uses of 1.

[0081] In addition, you can set default values ​​or default values ​​for the key generation parameters. When no key generation parameters are specified, the preset default values ​​can be used as the key generation parameters.

[0082] In one illustrative embodiment illustrated in this specification, multiple key pairs can be managed and maintained simultaneously in the cloud server. The cloud server can be managed by multiple user accounts, and the same user account can send multiple remote management commands to remotely manage one or more programs on the cloud server. Therefore, multiple key pairs can be managed and maintained simultaneously in the cloud server to encrypt and decrypt different remote management commands.

[0083] Specifically, when generating key pairs, a unique key number can be assigned to each key pair as identification information. The key pair corresponding to the key can be determined based on the key number. Typically, the key number can be a number or a string; the key number can be randomly generated or generated according to a preset generation algorithm, and this instruction does not impose any specific limitations.

[0084] When maintaining key pairs in a cloud server, the key pairs are associated with their key numbers. When a remote management request is received from a user, the key number and public key corresponding to the key pair are sent to the user. After the user encrypts the remote management command using the public key, the user sends the key number and the encrypted remote management command together. When the cloud server receives the encrypted remote management command, it can determine the private key in the key pair that encrypted the remote management command based on the key number and decrypt it.

[0085] In one illustrative embodiment shown in this specification, instead of setting a dedicated key number, the public key of the key pair can be used as the key number. When sending encrypted remote management commands, the user can send the public key along with the command, so that the cloud server can determine the corresponding private key based on the public key.

[0086] Please see Figure 4 , Figure 4 An interactive diagram illustrating an embodiment of a cloud server remote management method according to this specification is shown schematically.

[0087] Typically, a proxy service can be deployed on a cloud server. This proxy service is usually a standard service provided by the cloud service provider, used to offer users an API interface for communicating with the cloud server. When users communicate with the cloud server, they do so by calling the API interface corresponding to the proxy service. This proxy service can remain continuously running to ensure the effectiveness of communication.

[0088] Specifically, this API interface can be provided by a cloud service provider. Users can call this API through a cloud gateway connected to their client to send remote management commands to the cloud server. The remote management commands sent by the user can pass through the cloud gateway, be stored by the cloud service management server, and then notify the aforementioned proxy service on the cloud server to receive and execute them.

[0089] Remote management requests and commands sent by users to the cloud server are all sent to the proxy service through this API interface, and the proxy service returns the public key or the execution result of the remote management command.

[0090] This proxy service can also authenticate information sent to the cloud server to ensure security. For example, remote management requests and commands sent by users must be authenticated by the proxy service before they can be passed to the cloud server for execution.

[0091] The cloud server also deploys a key management service for managing key pairs. This key management service is typically a standard service provided by the cloud service provider.

[0092] The key management service is responsible for generating key pairs and their corresponding key numbers, and for maintaining and managing them. To ensure the security of the key pairs, especially the private key, the key pairs can be maintained in the memory space corresponding to the key management service. The private key in the key pair is always maintained only within this key management service and is never output to the outside world in any form to ensure security.

[0093] Upon receiving a remote management command encrypted with a public key, the key management service uses the private key corresponding to the public key to decrypt the private information in the remote management service.

[0094] The key management service can generate key pairs based on the key pair generation parameters in the remote management request, and associate and store key generation parameters such as key validity period and key usage count with the key pairs.

[0095] For example, a key pair management service can maintain key pairs in the form of the following table:

[0096] 0x00a1 <Public Key 1> [[ID=0ID=0]]<Private Key 1> 1675309138 1 0x0a2c <Public key 2> <Private key 2> 1675308562 2

[0097] The validity period can be represented using a timestamp or natural time.

[0098] Each time the key management service completes the decryption of the remote management service to enable its execution, it can update the remaining usage count of the private key used for decryption and delete the key pair with 0 remaining usage counts, no longer maintaining or managing them.

[0099] It can also compare the current time with the validity period of the key pair to determine whether each key pair in maintenance and management has exceeded its validity period, and delete the key pair that has exceeded its validity period and stop maintaining and managing it.

[0100] Furthermore, when all key pairs maintained by the key management service have zero remaining uses or have exceeded their expiration dates, the key management service can delete all key pairs it maintains; at this point, the key management service will no longer maintain any key pairs. When the key management service is not maintaining or managing any key pairs, it can terminate the key management service until a new remote management request is received, in order to save resource overhead.

[0101] The following combination Figure 4 This paper introduces a specific implementation of a remote management method for cloud servers.

[0102] User 40 communicates with the cloud server by calling the API interface corresponding to the proxy service 42 through the cloud service system 41.

[0103] The methods for remote management of cloud servers may specifically include the following processes.

[0104] 401. The user invokes the API interface corresponding to the proxy service to send a remote management request to the target cloud server. The specific content of the remote management request may include: starting the remote management service 44, and requesting the public key and its key number of the new key from the key management service based on the given key generation parameters.

[0105] 402. The cloud service system verifies the legality of the aforementioned remote management request, including verifying the user's identity and the legality of the request content; after verification, the system sends the aforementioned remote management request to the proxy service corresponding to the target cloud server.

[0106] 403. After receiving the above remote management request, the agent service creates and executes a new script, Remote Management Request Script 43;

[0107] 404. The Remote Management Request script starts the Remote Management service so that it requests the public key and key number of the new key from the Key Management service;

[0108] 405. The remote management service locates the actual process corresponding to the key management service and sends the request to generate a key pair, as well as the key generation parameters, to the key management service through inter-process communication.

[0109] 406. Upon receiving a request from the remote management service, the key management service generates an asymmetric key based on the aforementioned key generation parameters and generates a corresponding key number. The public key, private key, corresponding key number, key validity period, key usage count, and other key generation parameters of the generated asymmetric key are maintained in the memory space corresponding to the key management service. Furthermore, the public key and corresponding key number of the generated key pair are sent to the aforementioned remote management service via inter-process communication.

[0110] 407. After receiving the public key and key number, the remote management service prints them as standard output to return the aforementioned remote management request script;

[0111] 408. The remote management request script outputs the public key and key number of the remote management service as standard output;

[0112] 409. The proxy service submits the execution results and output of the remote management request script to the cloud service system; the cloud service system can submit the public key and key number to the output of the remote management request script.

[0113] 410. Users can obtain the output of the remote management request script corresponding to the remote management request from the cloud service system, and can obtain the public key and key number from it;

[0114] 411. The user uses a public key to encrypt the private content in the remote management command and calls the corresponding API interface of the proxy service to send the encrypted remote management command to the target cloud server; the remote management command carries the key number;

[0115] 412. The cloud service system verifies the legality of the above remote management commands, including verifying the user's identity and the legality of the command content; after verification, the system sends the above remote management commands to the proxy service corresponding to the target cloud server.

[0116] 413. After receiving the above remote management request, the agent service creates and executes a new script, remote management command script 46;

[0117] 414. The remote management request script starts the remote management service so that it requests the key management service to decrypt the encrypted remote management command;

[0118] 415. The remote management service locates the actual process corresponding to the key management service, and sends the request to decrypt the encrypted remote management command, the encrypted privacy content, and the key number to the key management service through inter-process communication;

[0119] 416. When the key management service receives a request from the remote management service, it finds the private key in the key pair corresponding to the key number, uses the private key to decrypt the encrypted privacy content, and sends the decrypted privacy content to the aforementioned remote management service through inter-process communication.

[0120] 417. The remote management service obtains the decrypted private content, prints it to standard output, and executes remote management commands based on the decrypted private content in the standard output to manage the cloud server;

[0121] 418. The remote management command script displays the execution results and output of remote management commands;

[0122] 419. The agent service submits the execution results and output of the remote management command script to the cloud service system;

[0123] 420. Users can obtain the execution results and outputs of the remote management command scripts corresponding to the remote management commands from the cloud service system.

[0124] In one exemplary embodiment shown in this description, the decrypted privacy content is represented in the form of variables, and the values ​​of the variables, i.e. the plaintext of the privacy information, are stored in the memory space corresponding to the remote management command script or remote management service.

[0125] The remote management service can access privacy information through the aforementioned variables to execute remote management commands and perform remote management of the cloud server.

[0126] Once the remote management command has been executed and the execution result and output have been returned and submitted to the cloud service system, the remote service script and remote management service can be terminated, their corresponding memory space will be released, and the plaintext of the privacy information in the remote management command will be deleted.

[0127] In cloud server management, various sub-accounts of users with cloud server management privileges may also view and audit the content of remote management commands. Through the above method, the private information in remote management commands is always represented in ciphertext or variable form, and is never stored in plaintext. It is only maintained in memory space, and once the memory space is released, it cannot be viewed in any way. Therefore, through this method, no one (including cloud service providers and users themselves) can obtain the private key or the plaintext of the private information in the remote management commands, so no one can view or decrypt the original private information, technically completely eliminating the possibility of privacy information leakage.

[0128] Since key management services typically require continuous maintenance of key pairs and need to remain operational, and proxy services in cloud servers also need to operate continuously, key management services can be treated as a sub-service of proxy services, and all the functions of key management services can be integrated into proxy services.

[0129] The proxy service can provide the functions of the above-mentioned key management service, including generating key pairs, maintaining key pairs, and decrypting content encrypted with the public key using the private key in the key pair.

[0130] As mentioned above Figure 4 Taking the implementation method described above as an example, when the proxy service provides the above-mentioned key management service function, the remote management service started by the above-mentioned remote management request script can request the public key of the new key and its key number from the above-mentioned proxy service.

[0131] The remote management service can locate the actual process corresponding to the aforementioned proxy service and send the request to generate a key pair, as well as the key generation parameters, to the aforementioned proxy service through inter-process communication.

[0132] Upon receiving a request from the remote management service, the proxy service can generate an asymmetric key based on the key generation parameters and generate a corresponding key number. The public key, private key, corresponding key number, key validity period, key usage count, and other key generation parameters of the generated asymmetric key are maintained in the memory space corresponding to the proxy service. Furthermore, the public key and corresponding key number of the generated key pair are sent to the remote management service through inter-process communication.

[0133] Correspondingly, the remote management service started by the remote management request script can request the aforementioned proxy service to decrypt the encrypted remote management command;

[0134] The remote management service can locate the actual process corresponding to the aforementioned proxy service and send the request to decrypt the encrypted remote management command, the encrypted privacy content, and the key number to the aforementioned proxy service through inter-process communication.

[0135] Upon receiving a request from the remote management service, the aforementioned proxy service can locate the private key in the key pair corresponding to the key number, use the private key to decrypt the encrypted private content, and send the decrypted private content to the remote management service via inter-process communication. In an exemplary embodiment illustrated in this description, the remote management command can be used to modify the password of a target program on the cloud server based on a new password; the privacy information in the remote management command may include the new password.

[0136] Changing the password of the target program on the cloud server in this way can ensure password security.

[0137] In an exemplary embodiment of this specification, a cloud server remote management device is also provided. Please refer to... Figure 5 , Figure 5 This is a block diagram of a cloud server remote management device according to an embodiment of this specification.

[0138] The device may include the following components:

[0139] The key pair generation unit 510 is used to generate an asymmetric key pair for encrypting and decrypting privacy information in remote management commands in response to a remote management request sent by a user to the cloud server.

[0140] The public key sending unit 520 is used to store and maintain the key pair in the secure storage space on the cloud server, and to send the public key in the key pair to the user through the cloud service system.

[0141] The remote management unit 530 is configured to respond to a remote management command sent by the user and encrypted with the public key, decrypt the remote management command using the private key corresponding to the public key, and execute the decrypted remote management command to remotely manage the cloud server.

[0142] Optionally, the remote management request includes key generation parameters;

[0143] The key generation parameters include at least one of the following:

[0144] Key algorithm, key length, key validity period, number of times the key can be used;

[0145] The key pair generation unit 510 is specifically used for:

[0146] Based on the key generation parameters, an asymmetric key pair is generated for encrypting and decrypting privacy information in remote management commands.

[0147] The key pair generation unit 510 is specifically used for:

[0148] Generate an asymmetric key pair for encrypting and decrypting privacy information in remote management commands, and its corresponding key number;

[0149] The public key sending unit 520 is specifically used for:

[0150] The public key in the key pair, and the key number corresponding to the key pair, are sent to the user through the cloud service system;

[0151] The remote management command encrypted with the public key carries the key number.

[0152] Optionally, a proxy service corresponding to the cloud server is deployed on the cloud server; the proxy service is used to provide the user with an API interface for communicating with the cloud server.

[0153] The key pair generation unit 510 is specifically used for:

[0154] In response to a remote management request sent by a user to the agent service through the cloud service system;

[0155] The public key sending unit 520 is specifically used for:

[0156] The public key in the key pair is sent to the user by the proxy service through the cloud service system;

[0157] The remote management unit 530 is specifically used for:

[0158] In response to a remote management command encrypted with the public key sent by the user to the agent service through the cloud service system.

[0159] Optionally, a key management service for managing key pairs is also deployed on the cloud server;

[0160] The asymmetric key pair used to encrypt and decrypt privacy information in remote management commands is generated and managed by the key management service;

[0161] The key pair is maintained by the key management service in the memory space corresponding to the key management service.

[0162] Optionally, the key management service is a sub-service of the proxy service.

[0163] Optionally, the key pair generation unit 510 and the public key sending unit 520 are specifically used for:

[0164] In response to a received remote management request for the cloud server from a user, a remote management request script is created and executed.

[0165] The remote management request script is used for:

[0166] A key generation request is sent to the key pair management service so that the key pair management service generates an asymmetric key pair for encrypting and decrypting privacy information in remote management commands. The key pair is maintained in the isolated memory corresponding to the key pair management service, and the public key in the key pair is returned to the remote management request script.

[0167] Upon receiving the public key, it is sent to the user via the cloud service system as a response to the remote management request.

[0168] Optionally, the key pair generation unit 510 and the public key sending unit 520 are specifically used for:

[0169] In response to a remote management command encrypted with the public key sent by the user, a remote management command script is created and executed.

[0170] The remote management command script is used for:

[0171] Send a decryption request to the key pair management service so that the key pair management service can use the private key corresponding to the public key to decrypt the remote management command and return the decrypted remote management command to the remote management command script;

[0172] Execute the decrypted remote management command to remotely manage the cloud server.

[0173] Optionally, the privacy information contained in the decrypted remote management command returned is represented in the form of variables, and the values ​​of the variables are stored in the memory space corresponding to the remote management command script;

[0174] The remote management unit 530 is specifically used for:

[0175] By using the variable, the privacy information in the memory space is invoked to execute the decrypted remote management command for remote management of the cloud server.

[0176] Optionally, the apparatus further includes an invalid key deletion unit 540, used for:

[0177] Determine whether there are any invalid key pairs in the maintained key pairs that have been used 0 times or have exceeded their validity period;

[0178] If an invalid key pair exists, delete the invalid key pair.

[0179] Optionally, the apparatus further includes a service termination unit 550, for:

[0180] Determine if a key pair is being maintained;

[0181] If no key pair is being maintained, terminate the key management service.

[0182] Optionally, the remote management command is used to modify the password of a target program on the cloud server based on the new password;

[0183] The privacy information mentioned includes the new password;

[0184] The remote management of the cloud server includes modifying the password of the target program based on the new password.

[0185] The specific implementation process of the functions and roles of each unit in the above device can be found in the implementation process of the corresponding steps in the above method, and will not be repeated here.

[0186] For the apparatus embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The apparatus embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across at least one network unit. Some or all of the units can be selected to achieve the purpose of the solution in this specification according to actual needs. Those skilled in the art can understand and implement this without any inventive effort.

[0187] In exemplary embodiments of this specification, an embodiment of an apparatus and a terminal to which it is applied is also provided.

[0188] The embodiments of the device described in this specification can be applied to computer devices, such as servers or terminal devices. The device embodiments can be implemented in software, hardware, or a combination of both. Taking software implementation as an example, as a logical device, it is formed by the processor reading the corresponding computer program instructions from non-volatile memory into memory and executing them. From a hardware perspective, such as... Figure 6 As shown, Figure 6 This is a hardware structure diagram of a computer device 60 containing an embodiment of the present specification, except... Figure 6In addition to the processor 610, memory 630, network interface 620, and non-volatile memory 640 shown, the server or electronic device in which the device is located in the embodiment may also include other hardware depending on the actual function of the computer device, which will not be described in detail here.

[0189] In exemplary embodiments of this specification, a computer-readable storage medium is also provided, on which a program product capable of implementing the methods described above is stored. In some possible embodiments, various aspects of this specification may also be implemented as a program product including program code that, when the program product is run on a terminal device, causes the terminal device to perform the steps described in the "Exemplary Methods" section of this specification according to various exemplary embodiments.

[0190] The program product for implementing the above-described methods according to embodiments of this specification may employ a portable compact disc read-only memory (CD-ROM) and include program code, and may run on a terminal device, such as a personal computer. However, the program product of this specification is not limited thereto. In this document, a readable storage medium may be any tangible medium containing or storing a program that may be used by or in conjunction with an instruction execution system, apparatus, or device.

[0191] The program product may employ any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0192] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium, capable of sending, propagating, or transmitting programs for use by or in conjunction with an instruction execution system, apparatus, or device.

[0193] The program code contained on the readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, etc., or any suitable combination thereof.

[0194] Program code for performing the operations described herein can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, and conventional procedural programming languages ​​such as C or similar languages. The program code can execute entirely on the user's computing device, partially on the user's device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0195] The user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0196] While this specification contains numerous specific implementation details, these should not be construed as limiting the scope of any invention or the scope of the claims, but rather are primarily used to describe features of specific embodiments of a particular invention. Certain features described in at least one embodiment may also be implemented in combination in a single embodiment. On the other hand, various features described in a single embodiment may also be implemented separately in at least one embodiment or in any suitable sub-combination. Furthermore, while features may function in certain combinations as described above and even initially claimed in this way, one or at least one feature from a claimed combination may be removed from that combination in some cases, and a claimed combination may refer to a sub-combination or a variation thereof.

[0197] Similarly, although the operations are depicted in a specific order in the accompanying drawings, this should not be construed as requiring these operations to be performed in the specific order shown or sequentially, or requiring all illustrated operations to be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Furthermore, the separation of the various system units and components in the above embodiments should not be construed as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into at least one software product.

[0198] Thus, specific embodiments of the subject matter have been described. Other embodiments are within the scope of the appended claims. In some cases, the actions recited in the claims may be performed in a different order and still achieve the desired result. Furthermore, the processes depicted in the drawings are not necessarily shown in a specific order or sequence to achieve the desired result. In some implementations, multitasking and parallel processing may be advantageous.

[0199] The above description is merely a preferred embodiment of this specification and is not intended to limit this specification. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this specification should be included within the scope of protection of this specification.

Claims

1. A remote management method for a cloud server, applied to a cloud server created for a user on a cloud server-side platform, wherein the user communicates with the cloud server through a cloud service system; the method includes: In response to a remote management request sent by a user to the cloud server, an asymmetric key pair is dynamically generated for encrypting and decrypting privacy information in the remote management command; The key pair is stored and maintained in the secure storage space on the cloud server, and the public key in the key pair is sent to the user through the cloud service system. The private key in the key pair is always maintained in the cloud server. In response to a remote management command encrypted with the public key sent by the user, the system decrypts the remote management command using the private key corresponding to the public key and executes the decrypted remote management command to remotely manage the cloud server; wherein the cloud service system cannot obtain the plaintext of the privacy information contained in the remote management command.

2. The method according to claim 1, wherein, The remote management request includes key generation parameters; The key generation parameters include at least one of the following: Key algorithm, key length, key validity period, number of times the key can be used; The generation of the asymmetric key pair for encrypting and decrypting privacy information in remote management commands includes: Based on the key generation parameters, an asymmetric key pair is generated for encrypting and decrypting privacy information in remote management commands.

3. The method according to claim 1, wherein, The generation of the asymmetric key pair for encrypting and decrypting privacy information in remote management commands includes: Generate an asymmetric key pair for encrypting and decrypting privacy information in remote management commands, and its corresponding key number; Sending the public key from the key pair to the user via the cloud service system includes: The public key in the key pair, and the key number corresponding to the key pair, are sent to the user through the cloud service system; The remote management command encrypted with the public key carries the key number.

4. The method according to claim 1, wherein, A proxy service corresponding to the cloud server is deployed on the cloud server; the proxy service is used to provide the user with an API interface for communicating with the cloud server. The response to the received remote management request for the cloud server from the user includes: In response to a remote management request sent by a user to the agent service through the cloud service system; Sending the public key from the key pair to the user via the cloud service system includes: The public key in the key pair is sent to the user by the proxy service through the cloud service system; The response to the received remote management command encrypted with the public key sent by the user includes: In response to a remote management command encrypted with the public key sent by the user to the agent service through the cloud service system.

5. The method according to claim 4, wherein, A key management service for managing key pairs is also deployed on the cloud server; The asymmetric key pair used to encrypt and decrypt privacy information in remote management commands is generated and managed by the key management service; The key pair is maintained by the key management service in the memory space corresponding to the key management service.

6. The method according to claim 5, wherein, The key management service is a sub-service of the proxy service.

7. The method according to claim 5, wherein, In response to a received remote management request from a user to the cloud server, an asymmetric key pair is generated for encrypting and decrypting privacy information in the remote management commands. The key pair is stored and maintained in a secure storage space on the cloud server, and the public key of the key pair is sent to the user through the cloud service system, including: In response to a received remote management request for the cloud server from a user, a remote management request script is created and executed. The remote management request script is used for: A key generation request is sent to the key pair management service so that the key pair management service generates an asymmetric key pair for encrypting and decrypting privacy information in remote management commands. The key pair is maintained in the isolated memory corresponding to the key pair management service, and the public key in the key pair is returned to the remote management request script. Upon receiving the public key, it is sent to the user via the cloud service system as a response to the remote management request.

8. The method according to claim 5, wherein, The response to the received remote management command encrypted with the public key sent by the user includes decrypting the remote management command using the private key corresponding to the public key, and executing the decrypted remote management command to remotely manage the cloud server, including: In response to a remote management command encrypted with the public key sent by the user, a remote management command script is created and executed. The remote management command script is used for: Send a decryption request to the key pair management service so that the key pair management service can use the private key corresponding to the public key to decrypt the remote management command and return the decrypted remote management command to the remote management command script; Execute the decrypted remote management command to remotely manage the cloud server.

9. The method according to claim 8, wherein, The privacy information contained in the decrypted remote management command returned is represented in the form of variables, and the values ​​of the variables are stored in the memory space corresponding to the remote management command script; The execution of the decrypted remote management command for remote management of the cloud server includes: By using the variable, the privacy information in the memory space is invoked to execute the decrypted remote management command for remote management of the cloud server.

10. The method according to claim 5, wherein, After decrypting the remote management command using the private key corresponding to the public key, the method further includes: Determine whether there are any invalid key pairs in the maintained key pairs that have been used 0 times or have exceeded their validity period; If an invalid key pair exists, delete the invalid key pair.

11. The method according to claim 1, wherein, The remote management command is used to modify the password of a target program on the cloud server based on the new password. The privacy information mentioned includes the new password; The remote management of the cloud server includes modifying the password of the target program based on the new password.

12. A cloud server remote management device, applied to a cloud server created for a user on a cloud server side, wherein the user communicates with the cloud server through a cloud service system; the device comprises: A key pair generation unit is used to dynamically generate an asymmetric key pair for encrypting and decrypting privacy information in remote management commands in response to a remote management request sent by a user to the cloud server. The public key sending unit is used to store and maintain the key pair in the secure storage space of the cloud server, and send the public key of the key pair to the user through the cloud service system. The private key of the key pair is always maintained in the cloud server. A remote management unit is configured to respond to a remote management command sent by the user and encrypted with the public key, decrypt the remote management command using the private key corresponding to the public key, and execute the decrypted remote management command to remotely manage the cloud server; wherein the cloud service system cannot obtain the plaintext of the privacy information contained in the remote management command.

13. A storage medium having a computer program stored thereon, which, when executed, implements the steps of the method as described in any one of claims 1-11.

14. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein, When the processor executes the program, it implements the following method: wherein, when the processor executes the program, it implements the method as described in any one of claims 1-11.

Images