A method for extracting firmware from smart connected vehicles
By dynamically detecting permissions and setting firmware extraction monitoring programs, the problem of inflexible permission detection and encryption processing during the firmware extraction process of intelligent connected vehicles is solved, improving the efficiency and security of firmware extraction, ensuring the integrity and robustness of firmware sex.
Patent Information
- Application Number
- CN202411136380.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-19
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2044-08-19
AI Technical Summary
The prior art has insufficient permission detection and encryption processing in the process of extracting firmware of intelligent connected vehicles, resulting in low efficiency and insufficient security in firmware extraction, which cannot effectively prevent firmware tampering and attacks.
The first terminal establishes a communication connection with the vehicle computer system, dynamically detects the ADB permissions and port 21 opening, uses script instructions and encryption functions to perform firmware extraction, and sets a firmware extraction monitoring program in the vehicle computer system, and randomly selects the encryption function for data. Encrypt and decrypt, limit the number of decryption times to lock access.
Improves the flexibility and efficiency of firmware extraction, enhances the security of firmware extraction, avoids the risk of firmware theft or attack, and ensures the integrity and robustness of the firmware.
Smart Images

Figure CN118656840B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of intelligent network-connected vehicle firmware extraction, and in particular to a method for an intelligent network-connected vehicle firmware extraction process. Background Art
[0002] The Internet of Vehicles (IoV) is a branch of the Internet of Things (IoT). It exchanges and shares information through communication between vehicles, vehicles and infrastructure, vehicles and pedestrians, and vehicles and networks, thereby improving traffic efficiency, safety, and driving experience. With the rapid development of IoV technology, vehicle safety issues, especially network security issues, have become increasingly important. In the field of IoV security, firmware extraction is a crucial link. Firmware is software in embedded systems that is responsible for controlling the basic operations of hardware devices. For vehicles, firmware exists in various control units and electronic control units (ECUs), which are responsible for the startup, operation, and monitoring of the vehicle. Therefore, the security of firmware is directly related to the safety of the vehicle. First, firmware extraction is a prerequisite for identifying and fixing security vulnerabilities. By extracting firmware, security researchers can analyze the firmware code and discover potential security vulnerabilities and defects. For example, there may be problems such as unencrypted communication protocols, insufficient access control, and insecure boot processes. Once these problems are discovered, manufacturers can release patches and updates in a timely manner to fix these vulnerabilities. Second, firmware extraction helps with security testing and verification. After the firmware is extracted, the firmware can be simulated and tested to verify its security and stability under various conditions. This includes stress testing, penetration testing, and fault injection testing of the firmware. Through these tests, the robustness of the firmware in the face of attacks can be ensured. Firmware extraction is the basis for implementing integrity protection of connected car devices. By extracting the firmware, an integrity check value (such as a hash value) of the firmware can be generated. When the vehicle is started, the firmware can be detected by comparing the hash value of the current firmware with the original hash value to see if it has been tampered with. This helps prevent the implantation and spread of malware. Firmware extraction is also very important for the life cycle management of the vehicle. As the vehicle is used, the firmware may need to be updated to adapt to new features or fix known problems. By extracting and analyzing the firmware, the correctness and compatibility of the firmware update can be ensured, thereby avoiding problems that may occur during the update process.
[0003] Based on the above problems, this paper proposes a method for the firmware extraction process of intelligent connected vehicles. Summary of the invention
[0004] In view of the above problems, the present invention proposes a method for extracting firmware of intelligent connected vehicles, which specifically includes the following steps:
[0005] S1. Establishing a communication connection between the first terminal and the vehicle system;
[0006] The communication connection mode is a network connection or a USB connection;
[0007] S2. The first terminal sends a first instruction to the vehicle system;
[0008] The first instruction includes an ADB open verification instruction, extraction operation data and an encryption function;
[0009] S3. The vehicle system receives the first instruction, detects whether the vehicle system is open ADB permission, and feeds back the detection result to the first terminal;
[0010] S4. When the detection result is that the vehicle system opens ADB permissions, the first terminal connects to the vehicle system through the ADB tool and runs a script to extract the firmware in the vehicle system;
[0011] When the detection result is that the vehicle system does not open the ADB authority, executing step S5;
[0012] S5. The first terminal performs a port scan on the vehicle IP to determine whether the vehicle system has port 21 open;
[0013] If enabled, the first terminal uses the filezilla tool to connect to the vehicle system and extract the firmware in the vehicle system;
[0014] If it is not enabled, the vehicle system firmware must be extracted manually.
[0015] Furthermore, the step S2 specifically includes the following steps:
[0016] S21. The first terminal obtains multiple script instructions and encryption functions for the firmware extraction operation;
[0017] The multiple script instructions are sorted in order of execution;
[0018] The plurality of script instructions are used as extraction operation data;
[0019] The encryption function is a function for encrypting the firmware;
[0020] The first terminal stores a first encryption function and a second encryption function;
[0021] The first terminal randomly selects any one of the first encryption function and the second encryption function as the encryption function;
[0022] S22. The first terminal packages the multiple script instructions, encryption functions, and ADB open verification instructions, and encrypts the packaged data using the unselected encryption function of the first encryption function and the second encryption function, and uses the encrypted data as the first instruction;
[0023] S23. The first terminal sends the first instruction to the vehicle system.
[0024] Furthermore, the step S3 specifically includes the following steps:
[0025] S31. The vehicle system receives the first instruction, and uses the first decryption function and the second decryption function to decrypt the first instruction respectively, and the vehicle system records the number of decryptions for the first instruction. When the decryption is successful, step S32 is executed; when the vehicle system finds that the decryption is unsuccessful twice or the number of decryptions for the first instruction is greater than two times, the vehicle system locks the first instruction and prohibits any access operation to the first instruction;
[0026] Wherein, the vehicle system stores a first decryption function and a second decryption function; the first decryption function corresponds to the first encryption function, and the second decryption function corresponds to the second encryption function;
[0027] S32. The vehicle system extracts the ADB open verification instruction in the first instruction, extracts the operation data and the encryption function;
[0028] S33. The vehicle system detects whether the vehicle system is open ADB permissions, and feedback the detection results to the first terminal;
[0029] The detection results include: the vehicle system opens the ADB permission, and the vehicle system does not open the ADB permission.
[0030] Furthermore, the step S4 specifically includes the following steps:
[0031] S41. When the detection result is that the vehicle system opens ADB permissions, the first terminal connects to the vehicle system through the ADB tool;
[0032] S42. The first terminal determines whether the connection is abnormal; if no abnormality occurs, the first terminal runs a script to extract the firmware in the vehicle system;
[0033] If an abnormality occurs, the first terminal reconnects to the vehicle system through the ADB tool.
[0034] Furthermore, the first terminal runs a script to extract the firmware in the vehicle system, and the script specifically includes the following steps:
[0035] S4201. Create a new test directory under the vehicle system default directory and name the directory test;
[0036] The default directory is / data / local / tmp directory;
[0037] S4202. Search for files of the first file type in the root directory of the vehicle system;
[0038] The first file type is a file type;
[0039] S4203. Write the found file name into the file.txt file;
[0040] The file.txt file is pre-created in a preset directory;
[0041] S4204. Delete the record of the file.txt file itself from the file.txt file;
[0042] S4205. Save the remaining file names after the deletion operation in file.txt to file_filtered.txt;
[0043] The file_filtered.txt file is pre-created in a preset directory;
[0044] S4206. Rename the file_filtered.txt file to file.txt, and delete the file.txt file in step S4204;
[0045] S4207. Read each line in the file.txt file, and copy the file corresponding to each line to the test directory;
[0046] Each line in the file.txt file stores the file name of a file in step S4202;
[0047] S4208. Repeat step S4207 until all lines in file.txt are read, and then delete file.txt;
[0048] S4209. Find all directories under the root directory and write the directory names into the path.txt file;
[0049] The path.txt file is pre-created in a preset directory;
[0050] S4210. Delete the dev, mnt, proc, sys, sdcard, storage, resources, data, and run directories from the path.txt file, save the remaining directory names after deletion in the path.txt file to the path_filtered.txt file, and delete the path.txt file;
[0051] The path_filtered.txt file is pre-created in a preset directory;
[0052] S4211. Read each line in the path_filtered.txt file, compress the directory file corresponding to each line, and copy the compressed directory file to the test directory;
[0053] Each line in the path_filtered.txt file stores the directory name of a directory in step S4209;
[0054] S4212. Repeat step S4211 until all lines in the path_filtered.txt file are read, and then delete the path_filtered.txt file;
[0055] S4213. Send all files and directory files in the test directory to the specified directory in the first terminal;
[0056] The designated directory is a pre-designated directory in the first terminal.
[0057] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented in accordance with the contents of the specification. In order to make the above description and other purposes, features and advantages of the present invention more obvious and easy to understand, the preferred embodiments are specifically cited and described in detail as follows. BRIEF DESCRIPTION OF THE DRAWINGS
[0058] Various other advantages and benefits will become apparent to those of ordinary skill in the art by reading the detailed description of the preferred embodiments below. The accompanying drawings are only for the purpose of illustrating the preferred embodiments and are not to be considered as limiting the present invention. Moreover, the same reference symbols are used throughout the accompanying drawings to represent the same components. In the accompanying drawings:
[0059] Figure 1 The present invention is a flowchart of a method for extracting firmware of an intelligent connected vehicle. DETAILED DESCRIPTION
[0060] The exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments described herein. On the contrary, these embodiments are provided in order to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.
[0061] In the description of the present invention, unless otherwise clearly specified and limited, the terms "installed", "connected", "connected", "fixed" and the like should be understood in a broad sense, for example, it can be connected, detachably connected, or integrated; it can be mechanically connected or electrically connected; it can be directly connected or indirectly connected through an intermediate medium, it can be the internal connection of two elements or the interaction relationship between two elements. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.
[0062] The present invention proposes a method for extracting firmware of an intelligent connected vehicle, and the method specifically comprises the following steps:
[0063] S1. Establishing a communication connection between the first terminal and the vehicle system;
[0064] The communication connection mode is a network connection or a USB connection;
[0065] The first terminal is a laptop computer, a desktop computer, or the like.
[0066] S2. The first terminal sends a first instruction to the vehicle system;
[0067] The first instruction includes an ADB open verification instruction, extraction operation data and an encryption function;
[0068] S3. The vehicle system receives the first instruction, detects whether the vehicle system is open ADB permission, and feeds back the detection result to the first terminal;
[0069] S4. When the detection result is that the vehicle system opens ADB permissions, the first terminal connects to the vehicle system through the ADB tool and runs a script to extract the firmware in the vehicle system;
[0070] When the detection result is that the vehicle system does not open the ADB authority, executing step S5;
[0071] S5. The first terminal performs a port scan on the vehicle IP to determine whether the vehicle system has port 21 open;
[0072] If enabled, the first terminal uses the filezilla tool to connect to the vehicle system and extract the firmware in the vehicle system;
[0073] If it is not enabled, the vehicle system firmware must be extracted manually.
[0074] Furthermore, the step S2 specifically includes the following steps:
[0075] S21. The first terminal obtains multiple script instructions and encryption functions for the firmware extraction operation;
[0076] The multiple script instructions are sorted in order of execution;
[0077] The plurality of script instructions are used as extraction operation data;
[0078] The encryption function is a function for encrypting the firmware;
[0079] The first terminal stores a first encryption function and a second encryption function;
[0080] The first terminal randomly selects any one of the first encryption function and the second encryption function as the encryption function;
[0081] S22. The first terminal packages the multiple script instructions, encryption functions, and ADB open verification instructions, and encrypts the packaged data using the unselected encryption function of the first encryption function and the second encryption function, and uses the encrypted data as the first instruction;
[0082] S23. The first terminal sends the first instruction to the vehicle system.
[0083] Furthermore, the step S3 specifically includes the following steps:
[0084] S31. The vehicle system receives the first instruction, and uses the first decryption function and the second decryption function to decrypt the first instruction respectively, and the vehicle system records the number of decryptions for the first instruction. When the decryption is successful, step S32 is executed; when the vehicle system finds that the decryption is unsuccessful twice or the number of decryptions for the first instruction is greater than two times, the vehicle system locks the first instruction and prohibits any access operation to the first instruction;
[0085] Wherein, the vehicle system stores a first decryption function and a second decryption function; the first decryption function corresponds to the first encryption function, and the second decryption function corresponds to the second encryption function;
[0086] S32. The vehicle system extracts the ADB open verification instruction in the first instruction, extracts the operation data and the encryption function;
[0087] S33. The vehicle system detects whether the vehicle system is open ADB permissions, and feedback the detection results to the first terminal;
[0088] The detection results include: the vehicle system opens the ADB permission, and the vehicle system does not open the ADB permission.
[0089] Furthermore, the step S4 specifically includes the following steps:
[0090] S41. When the detection result is that the vehicle system opens ADB permissions, the first terminal connects to the vehicle system through the ADB tool;
[0091] S42. The first terminal determines whether the connection is abnormal; if no abnormality occurs, the first terminal runs a script to extract the firmware in the vehicle system;
[0092] If an abnormality occurs, the first terminal reconnects to the vehicle system through the ADB tool.
[0093] Furthermore, the first terminal runs a script to extract the firmware in the vehicle system, and the script specifically includes the following steps:
[0094] S4201. Create a new test directory under the vehicle system default directory and name the directory test;
[0095] The default directory is / data / local / tmp directory;
[0096] S4202. Search for files of the first file type in the root directory of the vehicle system;
[0097] The first file type is a file type;
[0098] S4203. Write the found file name into the file.txt file;
[0099] The file.txt file is pre-created in a preset directory;
[0100] S4204. Delete the record of the file.txt file itself from the file.txt file;
[0101] S4205. Save the remaining file names after the deletion operation in file.txt to file_filtered.txt;
[0102] The file_filtered.txt file is pre-created in a preset directory;
[0103] S4206. Rename the file_filtered.txt file to file.txt, and delete the file.txt file in step S4204;
[0104] S4207. Read each line in the file.txt file, and copy the file corresponding to each line to the test directory;
[0105] Each line in the file.txt file stores the file name of a file in step S4202;
[0106] S4208. Repeat step S4207 until all lines in file.txt are read, and then delete file.txt;
[0107] S4209. Find all directories under the root directory and write the directory names into the path.txt file;
[0108] The path.txt file is pre-created in a preset directory;
[0109] S4210. Delete the dev, mnt, proc, sys, sdcard, storage, resources, data, and run directories from the path.txt file, save the remaining directory names after deletion in the path.txt file to the path_filtered.txt file, and delete the path.txt file;
[0110] The path_filtered.txt file is pre-created in a preset directory;
[0111] S4211. Read each line in the path_filtered.txt file, compress the directory file corresponding to each line, and copy the compressed directory file to the test directory;
[0112] Each line in the path_filtered.txt file stores the directory name of a directory in step S4209;
[0113] S4212. Repeat step S4211 until all lines in the path_filtered.txt file are read, and then delete the path_filtered.txt file;
[0114] S4213. Send all files and directory files in the test directory to the specified directory in the first terminal;
[0115] The designated directory is a pre-designated directory in the first terminal.
[0116] Furthermore, before step S4213, the following steps are also included:
[0117] S42131. The vehicle system executes a firmware extraction monitoring program, which starts a first thread, obtains a preset directory in the first instruction to extract the operation data, and finds a test directory file in the preset directory;
[0118] S42132. The vehicle system uses the encryption function in the first instruction to encrypt the test directory file.
[0119] Furthermore, after step S4213, the following steps are also included:
[0120] After receiving the test directory file, the first terminal uses the decryption function corresponding to the encryption function in step S21 to decrypt the test directory file;
[0121] The first terminal stores a first decryption function corresponding to the first encryption function and a second decryption function corresponding to the second encryption function;
[0122] When the encryption function in step S21 is the first encryption function, the decryption function for decrypting the test directory file is the first decryption function;
[0123] When the encryption function in step S21 is the second encryption function, the decryption function for decrypting the test directory file is the second decryption function.
[0124] Furthermore, the firmware extraction monitoring program is pre-installed in the vehicle system by the first terminal;
[0125] In step S3, when the vehicle system receives the first instruction, the vehicle system controls the running of the firmware extraction monitoring program.
[0126] Furthermore, in step S3, when the vehicle system receives the first instruction, the vehicle system controls the running of the firmware extraction monitoring program, and the firmware extraction monitoring program starts the second thread. The second thread monitors the script instructions sent by the first terminal to the vehicle system, and compares the sent script instructions with the script instructions in the operation data extracted from the first instruction in the execution order. When any corresponding script instruction is inconsistent, the second thread controls to stop the operation of extracting the current firmware.
[0127] The beneficial effects of the invention are as follows:
[0128] 1. The present invention dynamically adjusts the firmware extraction method of the vehicle system by judging the ADB permission opening status of the vehicle system and the opening status of the 21st port, thereby improving the flexibility of firmware extraction in the vehicle system, eliminating the need for professional personnel to operate, and improving the efficiency of firmware extraction;
[0129] 2. The present invention proposes a method for extracting the firmware of the vehicle system, and uses script instructions to extract the firmware of the vehicle system, thereby improving the flexibility and efficiency of firmware extraction;
[0130] 3. The present invention realizes dynamic monitoring of the firmware extraction operation performed by the first terminal using the ADB tool by setting a firmware extraction monitoring program in the vehicle system, thereby preventing the firmware in the vehicle system from being attacked or stolen;
[0131] 4. In the present invention, the first terminal randomly selects an encryption function to encrypt the first instruction, and the vehicle system uses the first decryption function and the second decryption function to decrypt the first instruction respectively, and when the number of decryption times is greater than two, the vehicle system locks the first instruction, thereby avoiding the risk of firmware extraction caused by the theft or attack of the first instruction.
[0132] 5. In the present invention, the first thread encryption function in the firmware extraction monitoring program is used to encrypt the firmware to be sent to the first terminal, thereby improving the security of firmware extraction.
[0133] The above is only a preferred specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed by the present invention should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention shall be based on the protection scope of the claims.
Claims
1. A method for extracting firmware from an intelligent connected vehicle, characterized in that: The method specifically comprises the following steps: S1. Establishing a communication connection between the first terminal and the vehicle system; The communication connection mode is a network connection or a USB connection; S2. The first terminal sends a first instruction to the vehicle system; The first instruction includes an ADB open verification instruction, extraction operation data and an encryption function; S3. The vehicle system receives the first instruction, detects whether the vehicle system is open ADB permission, and feeds back the detection result to the first terminal; S4. When the detection result is that the ADB permission is opened for the vehicle system, the first terminal connects to the vehicle system through the ADB tool and runs the script to extract the firmware in the vehicle system; When the detection result is that the vehicle system does not open the ADB authority, executing step S5; S5. The first terminal performs a port scan on the vehicle IP to determine whether the vehicle system has port 21 open; If enabled, the first terminal uses the filezilla tool to connect to the vehicle system and extract the firmware in the vehicle system; If it is not enabled, the vehicle system firmware will be extracted manually; Wherein, the step S2 specifically includes the following steps: S21. The first terminal obtains multiple script instructions and encryption functions for the firmware extraction operation; The multiple script instructions are sorted in order of execution; The plurality of script instructions are used as extraction operation data; The encryption function is a function for encrypting the firmware; The first terminal stores a first encryption function and a second encryption function; The first terminal randomly selects any one of the first encryption function and the second encryption function as the encryption function; S22. The first terminal packages the multiple script instructions, encryption functions, and ADB open verification instructions, and encrypts the packaged data using the first encryption function and the unselected encryption function of the second encryption function, and uses the encrypted data as the first instruction; S23. The first terminal sends the first instruction to the vehicle system; Wherein, the step S3 specifically includes the following steps: S31. The vehicle system receives the first instruction, and uses the first decryption function and the second decryption function to decrypt the first instruction respectively, and the vehicle system records the number of decryptions for the first instruction. When the decryption is successful, step S32 is executed; when the vehicle system finds that the decryption is unsuccessful twice or the number of decryptions for the first instruction is greater than two times, the vehicle system locks the first instruction and prohibits any access operation to the first instruction; Wherein, the vehicle system stores a first decryption function and a second decryption function; the first decryption function corresponds to the first encryption function, and the second decryption function corresponds to the second encryption function; S32. The vehicle system extracts the ADB open verification instruction in the first instruction, extracts the operation data and the encryption function; S33. The vehicle system detects whether the vehicle system is open ADB permissions, and feedback the detection results to the first terminal; The detection result includes: the vehicle system opens the ADB permission, the vehicle system does not open the ADB permission; Wherein, the step S4 specifically includes the following steps: S41. When the detection result is that the vehicle system opens ADB permissions, the first terminal connects to the vehicle system through the ADB tool; S42. The first terminal determines whether the connection is abnormal; if no abnormality occurs, the first terminal runs a script to extract the firmware in the vehicle system; If an abnormality occurs, the first terminal reconnects to the vehicle system through the ADB tool; The first terminal runs a script to extract the firmware in the vehicle system, and the script specifically includes the following steps: S4201. Create a new test directory under the vehicle system default directory and name the directory test; The default directory is / data / local / tmp directory; S4202. Search for files of the first file type in the root directory of the vehicle system; The first file type is a file type; S4203. Write the found file name into the file.txt file; The file.txt file is pre-created in a preset directory; S4204. Delete the record of the file.txt file itself from the file.txt file; S4205. Save the remaining file names after the deletion operation in file.txt to file_filtered.txt; The file_filtered.txt file is pre-created in a preset directory; S4206. Rename the file_filtered.txt file to file.txt, and delete the file.txt file in step S4204; S4207. Read each line in the file.txt file, and copy the file corresponding to each line to the test directory; Each line in the file.txt file stores the file name of a file in step S4202; S4208. Repeat step S4207 until all lines in file.txt are read, and then delete file.txt; S4209. Find all directories under the root directory and write the directory names into the path.txt file; The path.txt file is pre-created in a preset directory; S4210. Delete the dev, mnt, proc, sys, sdcard, storage, resources, data, and run directories from the path.txt file, save the remaining directory names after deletion in the path.txt file to the path_filtered.txt file, and delete the path.txt file; The path_filtered.txt file is pre-created in a preset directory; S4211. Read each line in the path_filtered.txt file, compress the directory file corresponding to each line, and copy the compressed directory file to the test directory; Each line in the path_filtered.txt file stores the directory name of a directory in step S4209; S4212. Repeat step S4211 until all lines in the path_filtered.txt file are read, and then delete the path_filtered.txt file; S4213. Send all files and directory files in the test directory to the specified directory in the first terminal; The designated directory is a pre-designated directory in the first terminal.
2. A method for extracting firmware from an intelligent connected vehicle according to claim 1, characterized in that: Before step S4213, the following steps are also included: S42131. The vehicle system executes a firmware extraction monitoring program, which starts a first thread, obtains a preset directory in the first instruction to extract the operation data, and finds a test directory file in the preset directory; S42132. The vehicle system uses the encryption function in the first instruction to encrypt the test directory file.
3. A method for extracting firmware from an intelligent connected vehicle according to claim 2, characterized in that: After step S4213, the following steps are also included: After receiving the test directory file, the first terminal uses the decryption function corresponding to the encryption function in step S21 to decrypt the test directory file; The first terminal stores a first decryption function corresponding to the first encryption function and a second decryption function corresponding to the second encryption function; When the encryption function in step S21 is the first encryption function, the decryption function for decrypting the test directory file is the first decryption function; When the encryption function in step S21 is the second encryption function, the decryption function for decrypting the test directory file is the second decryption function.
4. A method for extracting firmware from an intelligent connected vehicle according to claim 3, characterized in that: The firmware extraction monitoring program is pre-installed in the vehicle system by the first terminal; In step S3, when the vehicle system receives the first instruction, the vehicle system controls the running of the firmware extraction monitoring program.
5. A method for extracting firmware from an intelligent connected vehicle according to claim 4, characterized in that: In step S3, when the vehicle system receives the first instruction, the vehicle system controls the running of the firmware extraction monitoring program, and the firmware extraction monitoring program starts the second thread. The second thread monitors the script instructions sent by the first terminal to the vehicle system, and compares the sent script instructions with the script instructions in the operation data extracted from the first instruction in the execution order. When any corresponding script instruction is inconsistent, the second thread controls to stop the operation of extracting the current firmware.
Citation Information
Patent Citations
Web interface data encryption and signing method and device, and server
CN106209886A
Encryption updating method and apparatus
CN108365957A
Method and system for conveniently capturing log based on Android system
CN113505055A
Remote file collection method and device based on embedded operating system
CN114860660A
Identity verification system based on block chain
CN115118441A
