Bootloader TPM Detection for Secure Firmware Boot Switching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing electronic apparatuses face issues with secure boot processes when updating the bootloader program, as power interruptions can lead to an inoperative status, necessitating infrequent updates to avoid such failures.
Innovation Solution
The bootloader determines the presence of a specific hardware module (TPM) and performs secure boot with an argument if installed, otherwise normal boot without, allowing the firmware to detect and perform processes specific to secure boot.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the bootloader program is updated to enable secure boot with TPM, then secure boot functionality is improved, but the risk of failure during update increases due to power interruption
Solution Approach 1:
The system performs preliminary detection of TPM installation status before initiating secure boot. The bootloader checks whether TPM is installed and configured beforehand, and only then proceeds to perform secure boot with the appropriate argument. This preliminary action prevents attempting secure boot when TPM is not available, avoiding update failures.
Solution Approach 2:
The system changes the boot parameter (argument) based on TPM installation status. When TPM is installed, the bootloader passes a specific argument to indicate secure boot setting; when TPM is not installed, it passes a different argument for normal boot. This parameter change allows the system to adapt its behavior based on hardware availability, preventing failures.
2Reliability
If secure boot is always performed, then firmware integrity is improved, but system compatibility decreases when TPM is not installed
Solution Approach 1:
The system dynamically adjusts its boot mode based on TPM installation status. The bootloader detects whether TPM is installed and accordingly determines whether to perform secure boot or normal boot. This dynamic adaptation allows the system to maintain firmware integrity when TPM is available while ensuring compatibility when TPM is not installed.
Solution Approach 2:
The system changes the boot argument parameter based on hardware configuration. When TPM is installed, a secure boot argument is passed; when not installed, a normal boot argument is passed. This parameter change enables the system to adapt between secure and non-secure boot modes, maintaining both integrity and compatibility.
3Reliability
If the bootloader is updated frequently to fix security issues, then security is improved, but the frequency of potential failures increases
Solution Approach 1:
The system implements feedback through detection of TPM installation status before each boot. The bootloader checks whether TPM is installed and uses this feedback to determine whether to perform secure boot. This feedback mechanism ensures that secure boot is only attempted when TPM is available, preventing failures while maintaining security.
Solution Approach 2:
The system uses parameter changes in the boot argument to control secure boot behavior. By passing different arguments based on TPM status, the system can enable secure boot for security updates while avoiding failures when TPM is not installed. This allows frequent security updates without increasing failure risk.
Data Source
AI summary
An electronic apparatus includes a bootloader and a firmware to be started by the bootloader. Further, the bootloader (a) determines whether a specific hardware module has been installed in the electronic apparatus or not when the electronic apparatus starts, and (b) if the specific hardware module has been installed, performs secure boot of the firmware with an argument that indicates secure boot setting, and if the specific hardware module has not been installed, performs normal boot of the firmware without the argument; and when the secure boot is performed, the firmware (a) on the basis of the argument, detects that the firmware is started under the secure boot, and (b) if the firmware detects that the firmware is started under the secure boot, performs a process to be performed in the secure boot.