Firmware signature method, signature server, firmware signature system and storage medium
By deploying the automatic interaction between the signature server in the signature server and the signature client in the personal computer, the problems of complexity of the firmware signature process and low resource utilization in the prior art are solved, and efficient and secure signature processing is achieved.
Patent Information
- Application Number
- CN202411375495.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-29
- Publication Date
- 2024-12-06
AI Technical Summary
The existing firmware signature technology relies on remote desktop login signature servers. The process is complex, the risk of errors is high, and the resources are limited, and it is unable to efficiently process multiple signature requests, which affects the overall efficiency.
Deploy the signature server in the signature server, and deploy the signature client in the personal computer that communicates with the signature server. Through the interaction between the signature server and the signature client, the signature service process is automated, and multiple signature clients are supported in parallel. Processing, using authentication mechanism and asynchronous execution method.
Simplify operations, reduce the error rate of manual intervention, improve signature processing efficiency and response speed, improve server resource utilization, enhance security, and is suitable for large-scale signature needs.
Smart Images

Figure CN119094139A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of firmware security technology, and in particular to a firmware signing method, a signing service end, a firmware signing system and a storage medium. Background Art
[0002] At present, under the high requirements of ensuring the security of electronic product chips, signing the firmware used in the product has become a crucial security measure. The core of this process is to use private keys for cryptographic signing to verify the integrity and source reliability of the firmware. In view of the extreme sensitivity of private keys and their strict security requirements, many companies have taken strict control measures to limit direct access to private keys and avoid arbitrarily assigning them to every employee involved in the signing business.
[0003] To address this challenge, enterprises generally adopt a centralized management solution, which is to deploy a limited number of signature servers that are authorized to access and operate private keys to perform firmware signing tasks. However, the current method of relying on remote desktop login to the signature server for signing operations is not only lengthy and complicated, but also highly dependent on manual execution of multiple steps, which greatly increases the risk of errors. In addition, due to the limited resources of the signature server and the fact that remote desktop connections usually do not support simultaneous logins, it is impossible to efficiently process multiple firmware signing requests in parallel, which seriously affects the overall signing efficiency.
[0004] Therefore, it is particularly urgent to innovate and optimize the existing firmware signature technology.
[0005] The above information is presented as background information only to assist with understanding the present disclosure and no determination or admission is made as to whether any of the above may be used as prior art with respect to the present disclosure. Summary of the invention
[0006] The present invention provides a firmware signing method, a signing service end, a firmware signing system and a storage medium to solve the problems existing in the prior art.
[0007] To achieve the above object, the present invention provides the following technical solutions:
[0008] In a first aspect, the present invention provides a firmware signing method, which is applied to a signing server, wherein the signing server is connected to at least two signing clients for communication, the signing server is deployed in a signing server, and the signing client is deployed in a personal computer, and the method comprises:
[0009] Receive the signature request and firmware to be signed sent by the signature client;
[0010] The signature resource is called to sign the firmware to be signed.
[0011] Furthermore, in the firmware signing method, the step of receiving the signing request sent by the signing client and the firmware to be signed includes:
[0012] Receive the signature request sent by the signature client;
[0013] authenticating the signature request;
[0014] After the authentication is passed, a file upload instruction is generated and sent to the signature client, and the file upload instruction is used to trigger the signature client to upload the firmware to be signed;
[0015] The firmware to be signed is received.
[0016] Further, in the firmware signing method, the step of authenticating the signature request includes:
[0017] Determine whether the authentication information carried in the signature request is consistent with the stored set authentication information;
[0018] If yes, it is determined that the signature request authentication is passed;
[0019] If not, it is determined that the signature request authentication fails.
[0020] Furthermore, in the firmware signing method, before the step of determining whether the authentication information carried in the signature request is consistent with the stored set authentication information, the method further includes:
[0021] Detecting whether the signature request carries authentication information, where the authentication information is information generated by the signature client and encapsulated in the signature request;
[0022] If yes, executing the step of determining whether the authentication information carried in the signature request is consistent with the stored set authentication information;
[0023] If not, it is determined that the signature request authentication fails.
[0024] Furthermore, in the firmware signing method, the step of calling the signature resource to sign the firmware to be signed is:
[0025] Add the firmware to be signed to a queue to be signed, and according to the first-in-first-out principle of the queue, call the signature resource to sign the firmware to be signed in the queue to be signed in turn;
[0026] Or, a multi-threaded parallel processing method is adopted to call the signature resource to sign the firmware to be signed.
[0027] Furthermore, in the firmware signing method, the step of calling the signature resource to sign the firmware to be signed is:
[0028] The signature resource is called to sign the firmware to be signed in an asynchronous execution manner.
[0029] Furthermore, in the firmware signing method, after the step of calling the signature resource to sign the firmware to be signed, the method further includes:
[0030] Receiving a download request sent by the signature client;
[0031] The successfully signed firmware is sent to the signing client.
[0032] In a second aspect, the present invention provides a signature server, comprising a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the firmware signature method provided in the first aspect is implemented.
[0033] In a third aspect, the present invention provides a firmware signing system, including a signing server and at least two signing clients;
[0034] The signature server is communicatively connected with at least two of the signature clients;
[0035] The signature service end is deployed in the signature server, and the signature client end is deployed in a personal computer;
[0036] The signature server is the signature server provided in the second aspect above.
[0037] In a fourth aspect, the present invention provides a storage medium comprising computer executable instructions, wherein the computer executable instructions are executed by a computer processor to implement the firmware signing method provided in the first aspect above.
[0038] Compared with the prior art, the present invention has the following beneficial effects:
[0039] The present invention provides a firmware signing method, a signing server, a firmware signing system and a storage medium. The signing server is deployed in a signing server, a signing client communicating with the signing server is deployed in a personal computer, and the signing service process is automated through the interaction between the signing server and the signing client. This not only simplifies the operation, reduces manual intervention and reduces the error rate, but also supports two or more signing clients to interact with the signing server at the same time, thus being able to cope with large-scale signing requirements, improve server resource utilization, and enhance overall signature processing efficiency and response speed. In addition, the method has good security and is suitable for large-scale promotion and application.
[0040] The present invention has other features and advantages, which will be apparent from or will be described in detail in the accompanying drawings and the following detailed description incorporated herein, which together serve to explain the specific principles of the invention. BRIEF DESCRIPTION OF THE DRAWINGS
[0041] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0042] Figure 1 It is a schematic diagram of the structure of the communication connection between the signature server and two signature clients mentioned in the first embodiment of the present invention;
[0043] Figure 2 This is one of the flowcharts of a firmware signing method provided in the first embodiment of the present invention;
[0044] Figure 3 This is a second flow chart of a firmware signing method provided in the first embodiment of the present invention;
[0045] Figure 4 This is one of the detailed flow diagrams of step S202 provided in the first embodiment of the present invention;
[0046] Figure 5 This is the second detailed flow diagram of step S202 provided in the first embodiment of the present invention;
[0047] Figure 6 This is a schematic diagram of the structure of a signature server provided by Embodiment 2 of the present invention;
[0048] Figure 7 It is a structural diagram of a firmware signature system provided in Embodiment 3 of the present invention. DETAILED DESCRIPTION
[0049] In order to explain in detail the possible application scenarios, technical principles, specific schemes that can be implemented, and the purposes and effects that can be achieved, the following is a detailed description of the specific embodiments listed in conjunction with the accompanying drawings. The embodiments described herein are only used to more clearly illustrate the technical solutions of the present application, and are therefore only used as examples, and cannot be used to limit the scope of protection of the present application.
[0050] Reference to "embodiment" herein means that the specific features, structures or characteristics described in conjunction with the embodiment may be included in at least one embodiment of the present application. The term "embodiment" appearing in various places in the specification does not necessarily refer to the same embodiment, nor does it particularly limit its independence or association with other embodiments. In principle, in the present application, as long as there is no technical contradiction or conflict, the various technical features mentioned in the embodiments can be combined in any way to form a corresponding implementable technical solution.
[0051] Unless otherwise defined, the technical terms used in this document have the same meanings as those generally understood by those skilled in the art to which this application belongs; the use of relevant terms in this document is only for describing specific embodiments and is not intended to limit this application.
[0052] In the description of this application, the term "and / or" is an expression used to describe the logical relationship between objects, indicating that three relationships may exist, for example, A and / or B, which means: A exists, B exists, and A and B exist at the same time. In addition, the character " / " in this article generally indicates that the objects before and after are in an "or" logical relationship.
[0053] In the present application, terms such as “first” and “second” are merely used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship of quantity, priority or sequence between these entities or operations.
[0054] Without further limitations, in this application, the words "include", "comprises", "has" or other similar expressions used in the sentences are intended to cover non-exclusive inclusion. These expressions do not exclude the presence of additional elements in the process, method or product including the elements, so that the process, method or product including a series of elements may include not only those limited elements, but also other elements not explicitly listed, or also include elements inherent to such process, method or product.
[0055] In this application, expressions such as "greater than", "less than", "exceed" and the like are understood to exclude the number itself; expressions such as "above", "below", "within" and the like are understood to include the number itself. In addition, in the description of the embodiments of this application, "multiple" means more than two (including two), and similar expressions related to "multiple" are also understood in this way, such as "multiple groups", "multiple times", etc., unless otherwise clearly and specifically limited.
[0056] In the description of the embodiments of the present application, space-related expressions used, such as "center", "longitudinal", "lateral", "length", "width", "thickness", "up", "down", "front", "back", "left", "right", "vertical", "horizontal", "vertical", "top", "bottom", "inside", "outside", "clockwise", "counterclockwise", "axial", "radial", "circumferential", etc., indicate the orientation or position relationship based on the orientation or position relationship shown in the specific embodiments or drawings, and are only for the convenience of describing the specific embodiments of the present application or facilitating the reader's understanding, and do not indicate or imply that the referred device or component must have a specific position, a specific orientation, or be constructed or operated in a specific orientation, and therefore cannot be understood as a limitation on the embodiments of the present application.
[0057] Unless otherwise expressly specified or limited, in the description of the embodiments of the present application, the terms such as "install", "connect", "connect", "fix", "set", etc. used should be understood in a broad sense. For example, the "connection" can be a fixed connection, a detachable connection, or an integrated setting; it can be a mechanical connection, an electrical connection, or a communication connection; it can be a direct connection, or it can be indirectly connected through an intermediate medium; it can be the internal connection of two elements or the interaction relationship between two elements. For technicians in the technical field to which the present application belongs, the specific meanings of the above terms in the embodiments of the present application can be understood according to the specific circumstances.
[0058] Embodiment 1
[0059] Embodiment 1 of the present invention provides a firmware signing method, which is applicable to the scenario of signing firmware. The method is applied to a signature server 1, wherein the signature server 1 is connected to at least two signature clients 2 (taking two as an example), wherein the signature server 1 is deployed in a signature server, and the signature client 2 is deployed in a personal computer, such as Figure 1 shown.
[0060] Please refer to Figure 2 , is a flowchart of a firmware signing method provided in Embodiment 1 of the present invention. The method specifically comprises the following steps:
[0061] S101: Receive a signature request and firmware to be signed sent by a signature client.
[0062] It should be noted that this step is the starting point of the entire signature process. The signature server must first receive a clear request from the signature client, namely the signature request, and obtain the firmware to be signed. This process ensures the timeliness and accuracy of data transmission and lays a solid foundation for subsequent signature processing.
[0063] The signature request is initiated by a personal computer through the HTTP protocol, which contains the basic information required for the signature, such as the identity of the requester, the firmware type, the signature type, etc. The signature client is responsible for receiving and responding to these requests, and then sending them to the signature server.
[0064] The firmware to be signed is the target file that needs to be digitally signed. It contains the software code, data or configuration information that needs to be protected. During the signing process, the firmware file will be encrypted or attached with a specific digital signature to ensure its integrity and the authenticity of the source.
[0065] The signature server is built using the Spring Boot framework, which enables the signature server to efficiently process HTTP requests and has good scalability and maintainability. At the same time, the signature server is designed with concurrent processing capabilities and can support parallel access by up to 200 signature clients, which ensures stable performance and response speed in high-concurrency scenarios.
[0066] S102: Calling a signature resource to sign the firmware to be signed.
[0067] It should be noted that after receiving a valid signature request and firmware, the signature server immediately calls the built-in signature resources (these resources may include key components such as encryption algorithm libraries and key management systems) to perform strict signing operations on the submitted firmware. This step reflects the core advantage of the present invention in terms of automated processing. Through an integrated service mechanism, the complex steps in the traditional manual signature process are greatly simplified, reducing the risk of human error.
[0068] It is worth noting that the embodiments of the present invention achieve direct communication and collaboration between the signature server and the signature client through a carefully designed architecture, without the need for a third party. This innovative design not only promotes the automation of the signature service process, but also significantly improves operational efficiency and accuracy. More importantly, it supports multiple signature clients to interact with the signature server at the same time, effectively responding to the challenges of large-scale signature requirements, greatly improving the utilization of server resources, and further accelerating the speed and responsiveness of the overall signature processing.
[0069] In addition, the scheme also fully considers security factors. Through the interaction between the signature server and the signature client, the data security and integrity in the signature process are ensured, providing a solid guarantee for wide promotion and application. In summary, the firmware signature method proposed in the present invention not only simplifies the operation process and reduces manual intervention, but also significantly improves the efficiency and security of signature processing, and has extremely high practical value and promotion prospects.
[0070] In an implementation of this embodiment, step S102 may be further refined as follows:
[0071] Add the firmware to be signed to a queue to be signed, and according to the first-in-first-out principle of the queue, call the signature resource to sign the firmware to be signed in the queue to be signed in turn;
[0072] Or, a multi-threaded parallel processing method is adopted to call the signature resource to sign the firmware to be signed.
[0073] It should be noted that this embodiment performs differentiated processing according to different numbers of signature resources.
[0074] When there is only one signature resource in the signature server, in order to avoid resource conflicts and ensure the orderly execution of tasks, the signature server will use a queue mechanism to manage the firmware to be signed. The specific steps are as follows:
[0075] First, the received firmware to be signed is added to a queue to be signed. This queue will be arranged in the order in which the firmware is received, that is, the first-in-first-out (FIFO) principle. Then, the signature server will take out the firmware from the head of the queue in turn and call the signature resource to sign it. Only one firmware can be processed at a time until all the firmware in the queue are signed.
[0076] When there are multiple signature resources in the signature server, in order to improve processing efficiency, the signature server will use multi-threaded parallel processing technology to execute multiple signature tasks simultaneously. The specific steps are as follows:
[0077] The signature server creates a corresponding number of threads according to the number of signature resources. Each thread will be bound to a signature resource to perform the signature task. The signature server can adopt a variety of strategies to distribute the firmware to be signed to each thread (such as average distribution, load balancing, etc.). Each thread will maintain its own list of pending firmware or directly take out the firmware from the global queue for processing. All threads start working at the same time, and each calls the bound signature resource to sign the assigned firmware. This can greatly shorten the overall signing time and improve the system throughput. When all threads have completed the signature task, the signature server can summarize the signature results and notify the signature client or perform subsequent processing.
[0078] Through the above refinement and optimization measures, the system can more flexibly respond to scenarios with different numbers of signature resources and ensure the efficient and orderly execution of signature tasks.
[0079] In an implementation of this embodiment, step S102 may be further refined as follows:
[0080] The signature resource is called to sign the firmware to be signed in an asynchronous execution manner.
[0081] It should be noted that the asynchronous execution between the signature client and the signature server means that when the signature server accepts the signature request and is ready to execute the signature process, the signature client does not need to wait in real time, but can obtain the task progress through regular inquiries. This mechanism allows the signature client to continue to perform other tasks while the signature server is processing the request, improving the responsiveness and efficiency of the signature client.
[0082] In one implementation of this embodiment, Figure 2 Based on the above, step S101 is further optimized. The explanations of the terms that are the same or corresponding to the above embodiments are not repeated here, namely:
[0083] Receive the signature request sent by the signature client;
[0084] authenticating the signature request;
[0085] After the authentication is passed, a file upload instruction is generated and sent to the signature client, and the file upload instruction is used to trigger the signature client to upload the firmware to be signed;
[0086] The firmware to be signed is received.
[0087] Based on the above optimization, Figure 3 As shown, a firmware signing method provided in this embodiment may specifically include the following steps:
[0088] S201: Receive a signature request sent by a signature client.
[0089] It should be noted that receiving the signature request from the signature client is the starting point for triggering the entire signature process, ensuring the timeliness and accuracy of subsequent operations.
[0090] S202: Authenticate the signature request.
[0091] It should be noted that even if the signature request initiated by the signature client communicating with the signature server has a certain degree of security and authenticity, in order to further improve security, after receiving the signature request, the signature server will then perform an authentication step to further verify the identity of the signature client and the legitimacy of its request. This step is a key link to further ensure the security of the signature process. Through strict identity authentication and permission review, unauthorized access and malicious operations are effectively prevented.
[0092] S203: after authentication is passed, generate a file upload instruction and send it to the signature client, wherein the file upload instruction is used to trigger the signature client to upload the firmware to be signed.
[0093] It should be noted that if the signature request passes the authentication, the signature server generates a file upload instruction and sends the instruction to the signature client. The instruction can prompt the signature client to upload the firmware to be signed to the signature server. This design optimizes the file transfer process, avoids unnecessary waiting time, and improves overall efficiency.
[0094] S204: Receive the firmware to be signed.
[0095] It should be noted that after receiving the file upload instruction, the signature client performs corresponding operations to upload the firmware to be signed to the signature server. The signature server then receives the firmware to be signed and prepares for subsequent signature processing.
[0096] S205: Call signature resources to sign the firmware to be signed.
[0097] It should be noted that after successfully receiving the firmware to be signed, the signature server calls the built-in signature resource to sign the firmware file. This step is the core of the signature process and ensures the integrity and source reliability of the firmware file.
[0098] In summary, through the optimization measures in this embodiment, the firmware signing method not only improves the security of the process (through the authentication mechanism), but also enhances the convenience of operation (through automatic generation and sending of file upload instructions). These improvements make the firmware signing process more efficient and reliable, can better meet the needs of large-scale signing, and improve the overall processing efficiency and response speed.
[0099] Please refer to Figure 4 In one implementation of this embodiment, Figure 3 Step S202 in the above is divided into more detailed steps to ensure the accuracy and rigor of the authentication process, and specifically includes the following steps:
[0100] S202.1. Determine whether the authentication information carried in the signature request is consistent with the stored set authentication information; if so, execute S202.2; if not, execute S202.3.
[0101] It should be noted that in this step, the signature server first parses the authentication information carried in the signature request. Authentication information usually includes user ID, password, token, timestamp, digital signature, etc., which are used to verify the identity and authority of the requester. The signature server then compares this information with the stored set authentication information. The set authentication information is set during system initialization or user registration, and contains the authentication data of legitimate users allowed to access the signature service.
[0102] When judging consistency, the signature server verifies whether the authentication information carried in the signature request is consistent with the stored set authentication information through encryption algorithms or database queries. This process is the core of authentication, ensuring that only authorized users can initiate valid signature requests. If they are consistent, it means that the signature request comes from a legitimate user and the user has the authority to initiate the signature request, so S202.2 is executed. If they are inconsistent, it means that the signature request may come from an illegal user or the request has been tampered with, so S202.3 is executed.
[0103] S202.2. Determine whether the signature request authentication is successful.
[0104] It should be noted that when the authentication information in the signature request is consistent with the stored set authentication information, the signature server determines that the signature request is authenticated. Subsequently, the signature server can continue to execute subsequent steps, such as generating a file upload instruction, receiving the firmware to be signed, etc.
[0105] S202.3. Determine that the signature request authentication fails.
[0106] It should be noted that when the authentication information in the signature request is inconsistent with the stored authentication information, the signature server determines that the signature request authentication fails. In this case, the signature server can take a series of security measures, such as logging, sending alarms, and refusing services, to prevent potential security risks. At the same time, the signature server can also return an error message to the signature client, prompting the user to re-authenticate or check the content of its request.
[0107] Through such detailed steps, not only can the security of the signature service be ensured, but also a smoother and more efficient signing experience can be provided to legitimate users.
[0108] Please refer to Figure 5 In one implementation of this embodiment, Figure 4 Specifically, a pre-step is added before step S202.1, as follows:
[0109] S202.0. Detect whether the signature request carries authentication information, where the authentication information is information generated by the signature client and encapsulated in the signature request; if so, execute S202.1; if not, execute S202.3.
[0110] It should be noted that this step is newly added to ensure that the signature request contains the necessary authentication information. The authentication information is generated by the signature client and encapsulated in the signature request and sent to the signature server for verification. The signature server first parses the signature request to check whether it contains the authentication information.
[0111] If the authentication information is carried, it means that the signature client has generated and sent the authentication information as required, and the signature server can continue to execute the next step S202.1 to verify the authentication information.
[0112] If the authentication information is not carried, it means that the signature request is incomplete or may come from an untrusted source. The signature server directly executes S202.3, determines that the signature request authentication fails, and may return an error message to the signature client.
[0113] S202.1. Determine whether the authentication information carried in the signature request is consistent with the stored set authentication information; if so, execute S202.2; if not, execute S202.3.
[0114] S202.2. Determine whether the signature request authentication is successful.
[0115] S202.3. Determine that the signature request authentication fails.
[0116] When the signature request does not carry authentication information or the carried authentication information is inconsistent with the set authentication information, the signature server determines that the authentication fails. In this case, the signature server should take appropriate security measures and record relevant information for subsequent audits or troubleshooting. At the same time, the signature server should return an error message to the signature client, prompting the user to re-authenticate or check the content of their request.
[0117] Through such optimization, the signature server can more strictly control access to the signature service, ensuring that only authorized users can initiate valid signature requests, thereby improving the security and reliability of the signature process.
[0118] In one implementation of this embodiment, after step S102, a further interaction mechanism with the signing client is provided so that the signing client can obtain the firmware that has been successfully signed. The method further includes:
[0119] Receive a download request sent by the signature client.
[0120] The successfully signed firmware is sent to the signing client.
[0121] It should be noted that during or after the asynchronous execution of the signature task, the signature server needs to listen for download requests from the signature client. These requests are usually sent via HTTP, WebSocket or other network communication protocols.
[0122] When receiving a download request, the signature server should verify the validity of the request, including the source of the request (such as IP address, signature client identifier, etc.), the requested firmware ID or signature task ID, etc., to ensure that only legitimate signature clients can download successfully signed firmware.
[0123] Once the validity of the download request is verified, the signature server will search the database for the corresponding successfully signed firmware based on the firmware ID or signature task ID in the request.
[0124] After finding the firmware, the signature server reads it from the storage location (such as the file system, database, cloud storage, etc.) and prepares to send it to the signature client through the network. In this process, the firmware may also need to be encrypted, compressed, etc. to improve transmission efficiency and security.
[0125] Finally, the signature server sends the successfully signed firmware to the signature client through the previously established network connection. During the sending process, the signature server can monitor the transmission status and take corresponding measures (such as retrying, reporting errors, etc.) when errors occur.
[0126] By adding the steps of receiving a download request and sending the successfully signed firmware, the method of this embodiment provides a complete firmware signing and downloading service for the signature client, further improving the user experience and the practicality of the system.
[0127] Although the terms such as signature server, signature client, signature, etc. are frequently used in this application, the possibility of using other terms is not excluded. These terms are used only to more conveniently describe and explain the essence of the present invention; interpreting them as any additional restrictions is contrary to the spirit of the present invention.
[0128] A firmware signing method provided by an embodiment of the present invention deploys a signature server in a signature server, deploys a signature client in a personal computer that is in communication with the signature server, and realizes automation of the signature service process through interaction between the signature server and the signature client, thereby not only simplifying operations, reducing manual intervention, and lowering error rates, but also supporting two or more signature clients to interact with the signature server at the same time, thereby being able to cope with large-scale signature requirements, improve server resource utilization, and enhance overall signature processing efficiency and response speed. In addition, it also has good security and is suitable for large-scale promotion and application.
[0129] Embodiment 2
[0130] Figure 6This is a structural diagram of a signature server provided in Embodiment 2 of the present invention. The signature server includes a processor 60, a memory 61, an input device 62, and an output device 63; the number of processors 60 in the signature server can be one or more. Figure 6 A processor 60 is taken as an example; the processor 60, the memory 61, the input device 62 and the output device 63 in the signature server can be connected by a bus or other means. Figure 6 The example of connecting through bus is taken in the following.
[0131] The memory 61, as a computer-readable storage medium, can be used to store software programs, computer executable programs and modules, such as program instructions / modules corresponding to the firmware signing method in the embodiment of the present invention (for example, receiving a signature request and a firmware to be signed sent by a signature client; calling a signature resource to sign the firmware to be signed). The processor 60 implements various functional applications and data processing of the signature server by running the software programs, instructions and modules stored in the memory 61, that is, implements the above-mentioned firmware signing method.
[0132] The memory 61 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system and at least one application required for a function; the data storage area may store data created according to the use of the terminal, etc. In addition, the memory 61 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 61 may further include a memory remotely arranged relative to the processor 60, and these remote memories may be connected to the signature service end via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
[0133] The input device 62 may be used to receive input digital or character information and generate key signal input related to user settings and function control of the signature server. The output device 63 may include a display device such as a display screen.
[0134] Embodiment 3
[0135] Please refer to Figure 7 , Embodiment 3 of the present invention provides a firmware signature system, including a signature server 100 and at least two signature clients 200;
[0136] The signature server is in communication connection with at least two of the signature clients 200;
[0137] The signature service end 100 is deployed in a signature server, and the signature client 200 is deployed in a personal computer;
[0138] The signature server 100 is the signature server provided in the second embodiment.
[0139] Workflow
[0140] Signature request: The user selects the firmware to be signed through the signature client 200 and fills in the necessary signature information (such as signature algorithm, certificate selection, etc.). Then, the signature client 200 uses asynchronous execution to package this information into a signature request and sends it to the signature server 100.
[0141] Signature processing: After receiving the signature request, the signature server 100 first performs authentication verification. After the verification is passed, the signature server 100 adds the firmware to be signed to the processing queue and calls the signature resource to perform signature processing on it.
[0142] Result notification: After the signature is completed, the signature server 100 saves the signature result (signed firmware) and notifies the signature client 200 through a certain mechanism (such as callback function, message queue, HTTP response, etc.). After receiving the notification, the client can download the signed firmware file from the signature server 100.
[0143] Firmware download: The signature client 200 initiates a download request to obtain the signed firmware according to the notification of the signature server 100 or after a timed inquiry. After receiving the download request, the signature server 100 sends the firmware file to the signature client 200.
[0144] The advantages are:
[0145] Centralized management: The signature server 100 centrally processes all signature requests, facilitating unified management and maintenance.
[0146] Efficient processing: Asynchronous execution and multi-threaded parallel processing technology are used to improve the processing efficiency of signature tasks.
[0147] High security: Built-in authentication mechanism ensures that only legitimate clients can initiate signature requests, preventing illegal access and tampering.
[0148] Flexible expansion: The system supports multiple signature clients 200 to access simultaneously, and the processing capacity of the signature server 100 can be expanded as needed.
[0149] Embodiment 4
[0150] Embodiment 4 of the present invention provides a computer-readable storage medium on which computer-executable instructions are stored. When the instructions are executed by a processor, the firmware signing method provided in all the embodiments of the present application is implemented.
[0151] Any combination of one or more computer-readable media may be used. A computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. A computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In this document, a computer-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, device, or device.
[0152] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, which carry computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.
[0153] Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
[0154] Computer program code for performing the operations of the present invention may be written in one or more programming languages or a combination thereof, including object-oriented programming languages such as Java, Smalltalk, C++, and conventional procedural programming languages such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).
[0155] Finally, it should be noted that although the above embodiments have been described in the specification and drawings of this application, this does not limit the scope of patent protection of this application. All technical solutions generated by replacing or modifying equivalent structures or equivalent processes based on the essential concept of this application using the contents recorded in the specification and drawings of this application, as well as directly or indirectly implementing the technical solutions of the above embodiments in other related technical fields, are included in the scope of patent protection of this application.
Claims
1. A firmware signing method, applied to a signature server, wherein the signature server is connected to at least two signature clients for communication, the signature server is deployed in a signature server, and the signature client is deployed in a personal computer, characterized in that: The method comprises: Receive the signature request and firmware to be signed sent by the signature client; The signature resource is called to sign the firmware to be signed.
2. The firmware signing method according to claim 1, characterized in that: The step of receiving the signature request and the firmware to be signed sent by the signature client comprises: Receive the signature request sent by the signature client; authenticating the signature request; After the authentication is passed, a file upload instruction is generated and sent to the signature client, and the file upload instruction is used to trigger the signature client to upload the firmware to be signed; The firmware to be signed is received.
3. The firmware signing method according to claim 2, characterized in that: The step of authenticating the signature request comprises: Determine whether the authentication information carried in the signature request is consistent with the stored set authentication information; If yes, it is determined that the signature request authentication is passed; If not, it is determined that the signature request authentication fails.
4. The firmware signing method according to claim 3, characterized in that: Before the step of determining whether the authentication information carried in the signature request is consistent with the stored set authentication information, the method further includes: Detecting whether the signature request carries authentication information, where the authentication information is information generated by the signature client and encapsulated in the signature request; If yes, executing the step of determining whether the authentication information carried in the signature request is consistent with the stored set authentication information; If not, it is determined that the signature request authentication fails.
5. The firmware signing method according to claim 1, characterized in that: The steps of calling the signature resource to sign the firmware to be signed are: Add the firmware to be signed to a queue to be signed, and according to the first-in-first-out principle of the queue, call the signature resource to sign the firmware to be signed in the queue to be signed in turn; Or, a multi-threaded parallel processing method is adopted to call the signature resource to sign the firmware to be signed.
6. The firmware signing method according to claim 1, characterized in that: The steps of calling the signature resource to sign the firmware to be signed are: The signature resource is called to sign the firmware to be signed in an asynchronous execution manner.
7. The firmware signing method according to claim 1, characterized in that: After the step of calling the signature resource to sign the firmware to be signed, the method further includes: Receiving a download request sent by the signature client; The successfully signed firmware is sent to the signing client.
8. A signature server, comprising a memory and a processor, wherein the memory stores a computer program, characterized in that: When the processor executes the computer program, the firmware signing method according to any one of claims 1 to 7 is implemented.
9. A firmware signature system, characterized in that: Includes a signature server and at least two signature clients; The signature server is communicatively connected with at least two of the signature clients; The signature service end is deployed in the signature server, and the signature client end is deployed in a personal computer; The signature server is the signature server as claimed in claim 8.
10. A storage medium containing computer executable instructions, characterized in that: The computer executable instructions are executed by a computer processor to implement the firmware signing method according to any one of claims 1 to 7.
