CN112784275A - Electronic device, cloud deployment system of boot image and method thereof - Google Patents
Electronic device, cloud deployment system of boot image and method thereof Download PDFInfo
- Publication number
- CN112784275A CN112784275A CN201911060258.XA CN201911060258A CN112784275A CN 112784275 A CN112784275 A CN 112784275A CN 201911060258 A CN201911060258 A CN 201911060258A CN 112784275 A CN112784275 A CN 112784275A
- Authority
- CN
- China
- Prior art keywords
- electronic device
- boot
- boot image
- images
- destination files
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 45
- 238000004891 communication Methods 0.000 claims description 40
- 208000033748 Device issues Diseases 0.000 claims description 2
- 238000012795 verification Methods 0.000 claims description 2
- 230000006870 function Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 4
- 230000004913 activation Effects 0.000 description 3
- 230000007547 defect Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/57—Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
- H04L63/0442—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption
Abstract
A cloud deployment system and method for a boot image are provided. The server includes a storage medium and a control circuit. The electronic device is used for sending a request instruction. The storage medium is used for storing a plurality of starting images, each starting image comprises a plurality of destination files, and the combination sequence of the destination files of each starting image is different from the combination sequence of the destination files of other starting images. The control circuit is used for returning one of the starting images to the electronic device according to the request instruction, and the electronic device executes the received starting image.
Description
Technical Field
The present disclosure relates to the field of cloud booting, and in particular, to an electronic device with a booting image deployed in a cloud, a system and a method for cloud deployment of the booting image.
Background
The electronic device in daily use today needs to execute a boot image to boot the operating system and program of the electronic device during a boot process, and the boot image is commonly loaded in the electronic device when it is shipped out. However, manufacturers do not individually order the boot images for a single electronic device, but generally carry the same boot images for the same model or even the same type of electronic device, so as to facilitate management and maintenance. However, electronic devices with the same boot image may be a hacker attack pipeline due to the same program code.
When different electronic devices have the same boot image, a hacker can attack other electronic devices according to the defects by analyzing the boot image in one of the electronic devices and finding out the defects in the boot image. Moreover, in some cases, even a hacker does not need to insert malicious code into the electronic device, but instead applies code-reuse attack (code-reuse attack) to perform malicious attack on the electronic device. Specifically, the program code reuse attack is a hijacking control process, which uses the existing program code segment in the electronic device to spell out the attack method of malicious program.
Therefore, when hackers are confronted with a code reuse attack, electronic devices carrying the same boot image are easily attacked or, so to speak, are not protected, and for today where the issue of security is becoming more important, electronic devices having such defects are in need of improvement.
Disclosure of Invention
In view of the above, an electronic device for cloud deployment of a boot image, a cloud deployment system of a boot image, and a method thereof are provided.
According to some embodiments, a cloud deployment system for a boot image includes an electronic device and a server. The server includes a storage medium and a control circuit. The electronic device is used for sending a request instruction. The storage medium is used for storing a plurality of starting images, each starting image comprises a plurality of destination files, and the combination sequence of the destination files of each starting image is different from the combination sequence of the destination files of other starting images. The control circuit is used for returning one of the starting images to the electronic device according to the request instruction, and the electronic device executes the received starting image.
According to some embodiments, an electronic device includes a communication element and a controller. The controller is used for executing the input and output program to initialize the communication component. And after the communication element is initialized, the controller sends out a request command.
According to some embodiments, the storage medium further stores a plurality of source codes corresponding to the electronic device. The control circuit is used for compiling and assembling the source program code into a destination file, randomly arranging the destination file, establishing a connection address corresponding to the destination file, and obtaining one of the boot images.
According to some embodiments, the storage medium further stores a plurality of source codes corresponding to the electronic device. The server has a private key, and the electronic device has a public key corresponding to the private key. The control circuit is used for compiling and assembling the original program code into a destination file, randomly arranging the destination file, establishing a link address corresponding to the destination file, and encrypting by using a private key to obtain one of the boot images. The electronic device decrypts and executes the received boot image with the public key.
According to some embodiments, an electronic device with a cloud-deployed boot image includes a communication element and a controller. The controller is used for executing the input and output program to initialize the communication component. And after the communication element is initialized, the controller sends out a request instruction and executes the received starting-up image.
According to some embodiments, the electronic device with the cloud-deployed boot image further has a public key. The electronic device with the boot image deployed at the cloud end decrypts the boot image by using the public key and executes the received boot image.
According to some embodiments, a cloud deployment method of a boot image is suitable for an electronic device and a server. The cloud deployment method of the boot image comprises the following steps: the electronic device sends a request instruction; the server stores a plurality of starting images, each starting image comprises a plurality of destination files, and the combination sequence of the destination files of each starting image is different from the combination sequence of the destination files of other starting images; the server returns one of the boot images to the electronic device according to the request instruction; and the electronic device executes the received boot image.
According to some embodiments, before the electronic device issues the request instruction, the cloud deployment method of the boot image includes: the electronic device executes the input and output program to initialize the communication components of the electronic device; and after the communication element is initialized, the electronic device sends a request instruction.
According to some embodiments, the cloud deployment method of the boot image further includes a boot image obtaining method. The boot image obtaining method comprises the following steps: compiling and compiling a plurality of source program codes corresponding to the electronic device as a destination file; randomly arranging the destination files; establishing a link address corresponding to the destination file; and obtaining one of the boot images.
According to some embodiments, the cloud deployment method of the boot image further comprises a boot image obtaining and verifying method. The boot image obtaining and verifying method comprises the following steps: compiling and compiling a plurality of source program codes corresponding to the electronic device as a destination file; randomly arranging the destination files; establishing a link address corresponding to the destination file; encrypting by using a private key to obtain one of the boot images; and decrypting and executing the received boot image by using the public key, wherein the public key corresponds to the private key.
In summary, the cloud deployment system and the method for the boot image according to some embodiments of the present disclosure can deploy a plurality of different boot images in a server, and the server provides one of the boot images to the electronic device for execution according to a request command of the electronic device. The server deploys boot images obtained by randomly combining and arranging the destination files, so that the combination sequence of each boot image in the destination files is different, and the server randomly provides any boot image to the electronic device, so that the electronic device can obtain different boot images. Because the starting-up image files of the electronic device in each starting-up execution are different, the electronic device can be prevented from being attacked by hackers.
Drawings
Fig. 1 is a schematic diagram of a cloud deployment system for boot images according to some embodiments of the present disclosure.
Fig. 2 is a schematic diagram illustrating a boot image according to some embodiments of the disclosure.
Fig. 3 is a flowchart illustrating a cloud deployment method of a boot image according to some embodiments of the disclosure.
Fig. 4 is a flowchart illustrating a cloud deployment method of a boot image according to some embodiments of the disclosure.
Description of the symbols
10-boot image cloud deployment system
100 electronic device
120 controller
140 communication element
160 read-only storage element
180 random access memory device
R request instruction
200 server
220 control circuit
222 compiler
224 assembler
226 connector
240 storage medium
BI boot image
Library of LIB functions
DRV driver
OS operating system kernel
OBJ destination
SC original program code
S100-S140 steps
S110' step
Detailed Description
In this case, the term "coupled" and its derivatives may be used. In some embodiments, "coupled" may mean that two or more elements are in direct physical or electrical contact with each other, or that two or more elements are in direct electrical contact with each other. The term "coupled" may also be used to indicate that two or more elements co-operate or interact with each other.
Fig. 1 is a schematic diagram of a cloud deployment system 10 for boot images according to some embodiments of the present disclosure. The cloud deployment system 10 for boot images includes an electronic device 100 and a server 200. The electronic device 100 includes a controller 120, a communication device 140, a read-only storage device 160, and a random access storage device 180. The server 200 includes a control circuit 220 and a storage medium 240. The electronic apparatus 100 is configured to issue the request command R and execute the received boot image BI. The storage medium 240 of the server 200 is used for storing a plurality of boot images BI. The control circuit 220 of the server 200 is configured to transmit one of the power-on images BI back to the electronic device 100 according to the request command R. The electronic device 100 and the server 200 transmit signals or files via a network, and are not limited to wired or wireless transmission. In the electronic device 100, the controller 120 is coupled to the communication element 140, the read-only storage element 160 and the random access storage element 180. In the server 200, the control circuit 220 is coupled to the storage medium 240.
Fig. 2 is a schematic diagram of a boot image BI according to some embodiments of the disclosure. Referring to fig. 1 and fig. 2, in some embodiments, each boot image BI includes a plurality of destination files OBJ, and a combination sequence of the destination files OBJ of each boot image BI is different from a combination sequence of the destination files OBJ of other boot images BI. That is, the combination order of the destination files OBJ among the respective boot images BI is different. Therefore, each time the server 200 returns one of the boot images BI to the electronic device 100, the combination sequence of the destination files OBJ of the boot images BI received by the electronic device 100 is different. According to some embodiments, when the server 200 randomly selects the boot image BI to the electronic device 100, the electronic device 100 hardly receives the boot image BI with the same combination order of the destination OBJ.
Referring to fig. 1, in some embodiments, the cloud deployment system 10 of the boot image is configured to enable the electronic device 100 to obtain the boot image BI from the server 200 to execute the boot process. The electronic device 100 sends a request command R to the server 200, and the server 200 returns the boot image BI to the electronic device 100 according to the request command R. Specifically, the server 200 stores a plurality of boot images BI, and the server 200 returns any one of the boot images BI to the electronic device 100 according to the request command R. It should be noted that, according to some embodiments, the boot images BI stored in the server 200 can be executed by the electronic apparatus 100, but the boot images BI are obtained through a randomization process, so that the boot images BI are different. Since the server 200 randomly provides different boot images BI to the electronic device 100, each time the electronic device 100 sends the request command R, the boot images BI obtained by the electronic device 100 may be different, and therefore the electronic device 100 does not need to execute the same boot image BI each time to perform a boot procedure.
In some embodiments, the boot images BI are stored in the storage medium 240, and the control circuit 220 is configured to receive the request command R and randomly select one of the boot images BI from the storage medium 240 according to the request command R to be transmitted back to the electronic device 100. According to some embodiments, the control circuit 220 randomly selects the boot image BI according to the random number generation program. For example, the random number generating program outputs non-repeated random numbers to the boot images BI in the storage medium 240, each boot image BI has a corresponding random number, and the control circuit 220 selects the boot image BI with the largest random number to the electronic device 100.
It should be noted that, in some embodiments, the electronic apparatus 100 is not limited to whether or not there is a boot image BI loaded in itself. In a case where the electronic apparatus 100 itself does not carry the boot image BI, the electronic apparatus 100 sends a request command R to obtain the boot image BI each time the boot program is executed. In some embodiments, the electronic device 100 does not issue the request command R when the electronic device 100 is powered on, but issues the request command R according to an update requirement of the electronic device 100, for example, when the originally executed power-on image BI has been used for a specific lifetime or a specific number of times.
In some embodiments, when the electronic device 100 is powered on, the electronic device 100 first executes a Basic Input/Output System (BIOS) so that the communication element 140 sends the request command R after the initialization is completed. Specifically, the controller 120 is used for executing the input/output program to initialize the communication device 140, and issues the request command R after the communication device 140 is initialized. Specifically, the initialization of the communication component 140 represents the activation of the communication function of the communication component 140, and is not limited to the activation of the communication component 140 to a normal communication function or the activation of only a part of the communication function (e.g., only a part of the communication bandwidth, the communication speed, or the communication manner). The communication component 140 can be, for example, but not limited to, a wireless communication circuit, a wired communication circuit, or a circuit capable of both wireless communication and wired communication. In some embodiments, the request command R includes Identification (ID) information of the electronic apparatus 100, such as but not limited to a model number, a serial number, or related information that can be converted into a model number and/or a serial number of the electronic apparatus 100. According to some embodiments, the ROM device 160 is used to store I/O programs. The controller 120 obtains the storage I/O program from the ROM device 160 to perform initialization. The Read-Only Memory device 160 is, for example, a Read-Only Memory (ROM).
Referring to fig. 1 and fig. 2, in some embodiments, the electronic device 100 receives and runs the boot image BI to execute the boot program. Specifically, since the boot image BI includes a library LIB, a driver DRV and an operating System kernel (OS), wherein the library LIB includes functions of input/output, access, mathematical Operation, etc., the controller 120 executes the boot program to start the Operation of the operating System and the program in the electronic device 100. According to some embodiments, the driver DRV is used to activate the communication device 140 to normal communication functions. The random access memory 180 is used for storing the received boot image BI. The Random Access Memory device 180 is, for example, a flash Memory (RAM).
In some embodiments, the control circuit 220 of the server 200 includes a Compiler (Compiler)222, an assembler (Assembly)224, and a Linker (Linker) 226. The storage medium 240 of the server 200 is used for storing the boot image BI and a plurality of source codes SC corresponding to the electronic device 100. Wherein the source code SC is the code of the operating system and software. The control circuit 220 converts the source code SC into a plurality of destination files OBJ, randomly arranges the sequence of the destination files OBJ, and finally links the destination files OBJ to obtain the boot image BI. The process of converting the source code SC into the destination OBJ is completed by the compiling of the compiler 222 and the compiling of the assembler 224. The process of linking the destination OBJ to the boot image BI is completed by linking the addresses of the destination OBJ through the link 226 according to the sequence of the destination OBJ. According to some embodiments, the connector 226, such as the GNU connector, is connected to the address of the destination OBJ by a connector Script file (Linker Script) in the GNU connector. It should be noted that the address of the destination OBJ is, for example, but not limited to, a physical location or a virtual location in the electronic device 100. The connection method of the address of the destination OBJ is not limited to the use of a separate Jumper (jump) or the use of a mapping table lookup.
In some embodiments, each boot image BI stored in the storage medium 240 includes a plurality of destination files OBJ. The combination order of the destination files OBJ in any boot image BI is different from the combination order of the destination files OBJ in other boot images BI, that is, the combination order of the destination files OBJ between the boot images BI is different. Specifically, the boot image BI includes a library LIB, a driver DRV and an OS kernel, and the library LIB, the driver DRV and the OS kernel respectively include a plurality of destination files OBJ. In the process of obtaining the boot image BI by the control circuit 220, the control circuit 220 selects at least one of the library LIB, the driver DRV and the OS from the boot image BI to perform the object file OBJ random arrangement. The boot image BI may also be a library LIB, a driver DRV, and a destination OBJ in the OS, or two of the library LIB, the driver DRV, and the OS may be randomly arranged.
Referring to fig. 1, in some embodiments, the server 200 may generate a certain number of boot images BI in advance and store the boot images BI in the storage medium 240. In some embodiments, the server 200 can determine whether to generate more boot images BI for preparation according to the remaining number of boot images BI (i.e., the number of boot images BI that have not been returned to the electronic device 100). In some embodiments, when the server 200 receives the request command R, the control circuit 220 can generate the boot image BI according to the request command R to be provided to the electronic device 100 even if the storage medium 240 does not have the pre-generated boot image BI.
In some embodiments, the electronic device 100 has a public key (not shown), and the server 200 has a private key (not shown), wherein the public key corresponds to the private key. The process of obtaining the boot image BI by the control circuit 220 of the server 200 requires encryption by a private key, and the controller 120 of the electronic device 100 decrypts the received boot image BI by using a public key. Specifically, the control circuit 220 encrypts the boot image BI by using the private key to form a digital signature, and the encrypted boot image BI has the digital signature as a verification. The control circuit 220 then stores the encrypted boot image BI in the storage medium 240, that is, the boot image BI stored in the storage medium 240 is encrypted. After the electronic device 100 obtains the encrypted boot image BI, the electronic device 100 decrypts the boot image BI by using the public key to verify whether the digital signature is correct. When the digital signature is correct, the electronic device 100 can execute the verified boot image BI to perform a boot procedure. On the contrary, when the digital signature is incorrect, the electronic device 100 can reissue the request command R to the server 200 to re-send the boot image BI. In some embodiments, the electronic device 100 stores the boot image BI in the random access memory device 180 only when the digital signature is correct. According to some embodiments, the control circuit 220 does not encrypt the boot image BI during the process of generating the boot image BI, but the control circuit 220 encrypts the boot image BI by the private key after the control circuit 220 selects the boot image BI returned to the electronic device 100 from the storage medium 240.
In some embodiments, the cloud deployment system 10 of the boot image is not limited to only include one electronic device 100. For example, the cloud deployment system 10 of the boot image can include a plurality of electronic devices 100 at the same time, and is not limited to a single electronic device 100. The server 200 generates the booting images BI corresponding to the electronic devices 100 respectively according to the source codes SC corresponding to the electronic devices 100. Since the request command R issued by the electronic apparatus 100 has identification information, the server 200 can provide corresponding boot images BI according to different electronic apparatuses 100. According to some embodiments, the corresponding public key and private key in the cloud deployment system 10 of the boot image are not limited to one set, for example, the cloud deployment system 10 of the boot image can match different sets of public keys and private keys according to different types of the electronic devices 100. Alternatively, for a specific electronic device 100, the cloud deployment system 10 of the boot image can provide a single set of public and private keys to distinguish other electronic devices 100.
Fig. 3 is a flowchart illustrating a cloud deployment method of a boot image according to some embodiments of the disclosure. Reference to
Fig. 3 shows, in some embodiments, a cloud deployment method of a boot image, which is suitable for the electronic device 100 and the server 200 to execute. The cloud deployment method of the boot image comprises the following steps: the electronic device 100 issues a request command R (step S110); the server 200 stores a plurality of boot images BI, each boot image BI including a plurality of destination files OBJ, and a combination order of the destination files OBJ of each boot image BI being different from a combination order of the destination files OBJ of other boot images BI (step S120); the server 200 returns one of the boot images BI to the electronic device 100 according to the request command R (step S130); and, the electronic apparatus 100 executes the received boot image BI (step S140).
Fig. 4 is a flowchart illustrating a cloud deployment method of a boot image according to some embodiments of the disclosure. Referring to fig. 4, in some embodiments, the cloud deployment method of the boot image is suitable for the electronic device 100 and the server 200 to execute. The cloud deployment method of the boot image comprises the following steps: the electronic device 100 executes the input/output program to initialize the communication component 140 of the electronic device (step S100); after the communication component 140 is initialized, the electronic device 100 sends a request command R (step S110'); the server 200 stores a plurality of boot images BI, each boot image BI including a plurality of destination files OBJ, and a combination order of the destination files OBJ of each boot image BI being different from a combination order of the destination files OBJ of other boot images BI (step S120); the server 200 returns one of the boot images BI to the electronic device 100 according to the request command R (step S130); and, the electronic apparatus 100 executes the received boot image BI (step S140).
In summary, the cloud deployment system and the method for the boot image according to some embodiments of the present disclosure can deploy a plurality of different boot images in a server, and the server provides one of the boot images to the electronic device for execution according to a request command of the electronic device. The server deploys boot images obtained by randomly combining and arranging the destination files, so that the combination sequence of each boot image in the destination files is different, and the server randomly provides any boot image to the electronic device, so that the electronic device can obtain different boot images. Because the starting-up image files of the electronic device in each starting-up execution are different, the electronic device can be prevented from being attacked by hackers. In some embodiments, the cloud deployment system of the boot image and the method thereof further include a pair of corresponding public key and private key, the server encrypts the boot image with the private key, and the electronic device decrypts the boot image with the public key, so that the electronic device can also authenticate whether the boot image provided by the server is correct.
Claims (10)
1. A cloud deployment system for boot images, comprising:
an electronic device for sending a request command; and
a server, comprising:
a storage medium for storing a plurality of boot images, each boot image including a plurality of destination files, the combination order of the destination files of each boot image being different from the combination order of the destination files of the other boot images; and
and the control circuit is used for returning one of the starting images to the electronic device according to the request instruction, and the electronic device executes the received starting image.
2. The cloud deployment system for boot images of claim 1, wherein the electronic device comprises:
a communication element; and
a controller for executing an input/output program to initialize the communication device and sending the request command after the communication device is initialized.
3. The cloud deployment system of boot images as claimed in claim 1, wherein the storage medium further stores a plurality of source codes corresponding to the electronic device, and the control circuit is configured to compile and assemble the source codes into the destination files, randomly arrange the destination files, and establish connection addresses corresponding to the destination files to obtain one of the boot images.
4. The cloud deployment system of boot images as claimed in claim 1, wherein the storage medium further stores a plurality of source codes corresponding to the electronic device, the server has a private key, the electronic device has a public key corresponding to the private key, the control circuit is configured to compile and compile the source codes into the destination files, randomly arrange the destination files, establish connection addresses corresponding to the destination files, and encrypt the destination files with the private key to obtain one of the boot images, and the electronic device decrypts the received boot image with the public key and executes the received boot image.
5. An electronic device for cloud-deployed boot images, the electronic device comprising:
a communication element; and
a controller for executing an input/output program to initialize the communication device, and for issuing a request command and executing a received boot image after the communication device is initialized.
6. The electronic device of claim 5, further comprising a public key, wherein the electronic device with the cloud deployed boot image decrypts and executes the received boot image with the public key.
7. A cloud deployment method of a boot image is suitable for an electronic device and a server, and comprises the following steps:
the electronic device sends a request instruction;
the server stores a plurality of boot images, each boot image comprises a plurality of destination files, and the combination sequence of the destination files of each boot image is different from the combination sequence of the destination files of other boot images;
the server returns one of the boot images to the electronic device according to the request instruction; and
the electronic device executes the received boot image.
8. The cloud deployment method of the boot image according to claim 7, wherein before the electronic device issues the request instruction, the cloud deployment method of the boot image includes:
the electronic device executes an input/output program to initialize a communication component of the electronic device; and
after the communication element is initialized, the electronic device sends the request command.
9. The cloud deployment method of boot images according to claim 7, further comprising a boot image obtaining method, comprising:
compiling and assembling a plurality of source program codes corresponding to the electronic device into the destination files;
randomly arranging the target files;
establishing connection addresses corresponding to the destination files; and
one of the boot images is obtained.
10. The cloud deployment method of boot images of claim 7, further comprising a boot image acquisition and verification method, comprising:
compiling and assembling a plurality of source program codes corresponding to the electronic device into the destination files;
randomly arranging the target files;
establishing connection addresses corresponding to the destination files;
encrypting by using a private key to obtain one of the boot images; and
and decrypting and executing the received boot image by using a public key, wherein the public key corresponds to the private key.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911060258.XA CN112784275A (en) | 2019-11-01 | 2019-11-01 | Electronic device, cloud deployment system of boot image and method thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911060258.XA CN112784275A (en) | 2019-11-01 | 2019-11-01 | Electronic device, cloud deployment system of boot image and method thereof |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112784275A true CN112784275A (en) | 2021-05-11 |
Family
ID=75747204
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911060258.XA Pending CN112784275A (en) | 2019-11-01 | 2019-11-01 | Electronic device, cloud deployment system of boot image and method thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112784275A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070022184A1 (en) * | 2005-07-21 | 2007-01-25 | Rakesh Sharma | Method and apparatus for a secure network install |
| CN102939587A (en) * | 2010-03-31 | 2013-02-20 | 埃德图加拿大公司 | Method for linking and loading to protect applications |
| US20150234775A1 (en) * | 2014-02-14 | 2015-08-20 | Western Digital Technologies, Inc. | Enabling file oriented access on storage devices |
| CN107958155A (en) * | 2016-10-17 | 2018-04-24 | 深圳市中兴微电子技术有限公司 | A kind of system initialization method and device |
-
2019
- 2019-11-01 CN CN201911060258.XA patent/CN112784275A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070022184A1 (en) * | 2005-07-21 | 2007-01-25 | Rakesh Sharma | Method and apparatus for a secure network install |
| CN102939587A (en) * | 2010-03-31 | 2013-02-20 | 埃德图加拿大公司 | Method for linking and loading to protect applications |
| US20150234775A1 (en) * | 2014-02-14 | 2015-08-20 | Western Digital Technologies, Inc. | Enabling file oriented access on storage devices |
| CN107958155A (en) * | 2016-10-17 | 2018-04-24 | 深圳市中兴微电子技术有限公司 | A kind of system initialization method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10715335B2 (en) | Methods and apparatus to provide for efficient and secure software updates | |
| CN108475319B (en) | Birth certificate of device | |
| TWI454935B (en) | Booting and configuring a subsystem securely from non-local storage | |
| CA2655151C (en) | System and method for authenticating a gaming device | |
| US8560820B2 (en) | Single security model in booting a computing device | |
| CN101218588B (en) | Attachment device and arrangement with authenticable firmware and method for authenticating the firmware | |
| EP3575999A1 (en) | Secure booting a computing device | |
| US20080189554A1 (en) | Method and system for securing communication between a host computer and a secure portable device | |
| EP3291087A1 (en) | Apparatus and associated method for authenticating firmware | |
| CN107341003B (en) | Customization system implementing method, computer device and storage medium | |
| CN111512593B (en) | Semiconductor device, method of providing update data, method of receiving update data, and medium | |
| TWI768255B (en) | Cloud deployment boot image electronic device, boot image cloud deployment system and method thereof | |
| CN109491716A (en) | Start method and device, program storage method and device | |
| CN112784275A (en) | Electronic device, cloud deployment system of boot image and method thereof | |
| JP2017169147A (en) | Verification device, electronic apparatus, program, and verification system | |
| EP3460705A1 (en) | Distributed deployment of unique firmware | |
| Gedeon et al. | Secure boot and firmware update on a microcontroller-based embedded board | |
| CN116724309A (en) | Apparatus and communication method | |
| JP6988444B2 (en) | Initial setup method, secure element, device and program | |
| El Jaouhari et al. | Toward a generic and secure bootloader for IoT device firmware OTA update | |
| CN113330438A (en) | Secure code image distribution | |
| KR102387685B1 (en) | Secure Boot Verification Method and Secure Element for the Same | |
| US8291203B2 (en) | Using a live operating system to set up and configure an active management technology device | |
| US20230244789A1 (en) | Method for booting an electronic device | |
| Juhász et al. | Secure remote firmware update on embedded IoT devices |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |