Secure boot and firmware updates (OTA) in IOT Protocols - Mini Project: Build & Apply

Secure Boot and Firmware Updates (OTA)

📖 Scenario: You are working on an IoT device that needs to securely boot and update its firmware over the air (OTA). This ensures the device only runs trusted software and can receive updates safely.Imagine your smart home thermostat needs to check its firmware signature before starting and download new firmware updates securely.

🎯 Goal: Build a simple simulation of secure boot and OTA firmware update process using Python dictionaries and functions.You will create a data structure for firmware versions and signatures, configure a trusted signature, implement a check for secure boot, and simulate downloading and applying an OTA update.

📋 What You'll Learn

Create a dictionary with firmware versions and their signatures

Add a variable for the trusted signature

Write a function to verify firmware signature for secure boot

Simulate an OTA update by changing the firmware version and verifying it

Print the final firmware version after update

💡 Why This Matters

🌍 Real World

IoT devices must ensure they only run trusted firmware to prevent hacking. Secure boot checks firmware signatures before starting. OTA updates allow devices to get new features or fixes remotely and safely.

💼 Career

Understanding secure boot and OTA update processes is essential for IoT developers, embedded systems engineers, and DevOps professionals working with connected devices.

1

Create firmware data structure

Create a dictionary called firmware_versions with these exact entries: 'v1.0': 'sig123', 'v1.1': 'sig124', 'v2.0': 'sig125'

IOT Protocols

# Create the firmware_versions dictionary with exact keys and values
# Your code here

Hint

Use curly braces to create a dictionary with keys as version strings and values as signature strings.

2

Add trusted signature configuration

Create a variable called trusted_signature and set it to the string 'sig124'

IOT Protocols

firmware_versions = {'v1.0': 'sig123', 'v1.1': 'sig124', 'v2.0': 'sig125'}
# Set the trusted_signature variable to 'sig124'
# Your code here

Hint

Assign the exact string 'sig124' to the variable trusted_signature.

3

Implement secure boot check function

Write a function called secure_boot_check that takes a version parameter and returns True if the signature of that version in firmware_versions matches trusted_signature, otherwise returns False

IOT Protocols

firmware_versions = {'v1.0': 'sig123', 'v1.1': 'sig124', 'v2.0': 'sig125'}
trusted_signature = 'sig124'
# Define secure_boot_check(version) function to verify signature
# Your code here

Hint

Use the dictionary get method to get the signature for the version and compare it to trusted_signature.

4

Simulate OTA update and print result

Create a variable called current_version and set it to 'v1.0'. Then update current_version to 'v1.1' to simulate OTA update. Use secure_boot_check to verify the new version. Finally, print current_version if verification passes, otherwise print 'Update failed'

IOT Protocols

firmware_versions = {'v1.0': 'sig123', 'v1.1': 'sig124', 'v2.0': 'sig125'}
trusted_signature = 'sig124'

def secure_boot_check(version):
    return firmware_versions.get(version) == trusted_signature

# Simulate OTA update and print the current_version if secure boot check passes
# Your code here

Hint

Set current_version to 'v1.0', then update it to 'v1.1'. Use an if statement to check with secure_boot_check and print accordingly.

Practice

1. What is the main purpose of secure boot in IoT devices?

easy

A. To ensure only trusted software runs on the device

B. To speed up the device startup time

C. To allow any software to run without restrictions

D. To backup device data automatically

Solution

1. Step 1: Understand secure boot concept

   Secure boot checks the software's authenticity before running it on the device.

2. Step 2: Identify the main goal

   The goal is to prevent untrusted or malicious software from running.

3. Final Answer:

   To ensure only trusted software runs on the device -> Option A

4. Quick Check:

   Secure boot = trusted software only [OK]

Hint: Secure boot means only trusted software runs [OK]

Common Mistakes:

• Thinking secure boot speeds startup
• Believing secure boot allows any software
• Confusing secure boot with data backup

2. Which of the following is the correct command to verify a firmware update signature using openssl?

easy

A. openssl verify -CAfile ca.pem firmware.sig

B. openssl sign -verify firmware.bin

C. openssl dgst -verify ca.pem -signature firmware.sig firmware.bin

D. openssl check firmware.sig firmware.bin

Solution

1. Step 1: Recall openssl dgst verify syntax

   The correct syntax to verify a signature is: openssl dgst -verify [pubkey/cert] -signature [signature] [file].

2. Step 2: Match the command with syntax

   openssl dgst -verify ca.pem -signature firmware.sig firmware.bin matches this syntax exactly for verifying firmware signature.

3. Final Answer:

   openssl dgst -verify ca.pem -signature firmware.sig firmware.bin -> Option C

4. Quick Check:

   Verify signature = openssl dgst -verify [key] -signature [sig] [file] [OK]

Hint: Verify signature uses 'dgst -verify' and '-signature' flags [OK]

Common Mistakes:

• Using 'openssl sign' instead of 'dgst'
• Missing '-verify' or '-signature' flags
• Using wrong command like 'openssl check'

3. Given this pseudo-code for OTA update verification:

if verify_signature(firmware, signature, public_key):
    install_firmware(firmware)
else:
    reject_update()

What happens if the signature does not match?

medium

A. Update is rejected and not installed

B. Signature is ignored and update proceeds

C. Device reboots automatically

D. Firmware is installed anyway

Solution

1. Step 1: Analyze the conditional logic

   If verify_signature returns false, the else branch runs.

2. Step 2: Understand else branch action

   The else branch calls reject_update(), meaning the update is not installed.

3. Final Answer:

   Update is rejected and not installed -> Option A

4. Quick Check:

   Signature mismatch = reject update [OK]

Hint: If signature fails, update is rejected [OK]

Common Mistakes:

• Assuming firmware installs despite bad signature
• Thinking device reboots automatically
• Ignoring signature verification result

4. You wrote this OTA update script snippet:

if verify_signature(firmware, signature, public_key):
    install_firmware(firmware)
else:
    install_firmware(firmware)

What is the main problem here?

medium

A. Firmware is never installed

B. Signature verification function is missing

C. Public key is not used in verification

D. Firmware is installed even if signature verification fails

Solution

1. Step 1: Review the else branch code

   Both if and else branches call install_firmware(firmware).

2. Step 2: Understand security impact

   This means firmware installs regardless of signature check, breaking security.

3. Final Answer:

   Firmware is installed even if signature verification fails -> Option D

4. Quick Check:

   Else installs firmware = security risk [OK]

Hint: Else should reject update, not install firmware [OK]

Common Mistakes:

• Ignoring else branch code
• Assuming verification function is missing
• Confusing public key usage

5. You want to implement a secure OTA update system that:
- Verifies firmware signature
- Supports rollback if update fails
- Uses secure boot to prevent unauthorized code

Which sequence of steps best achieves this?

hard

A. Enable secure boot -> Install firmware -> Verify signature -> Rollback if failure

B. Enable secure boot -> Verify signature -> Install firmware -> Rollback if failure

C. Verify signature -> Install firmware -> Enable secure boot -> Rollback if failure

D. Install firmware -> Verify signature -> Enable secure boot -> Rollback if failure

Solution

1. Step 1: Enable secure boot first

   Secure boot must be active to prevent unauthorized code from running at startup.

2. Step 2: Verify firmware signature before installing

   Check the update is trusted before installation to avoid bad firmware.

3. Step 3: Install firmware and support rollback

   Install only if verified, and rollback if update fails to keep device safe.

4. Final Answer:

   Enable secure boot -> Verify signature -> Install firmware -> Rollback if failure -> Option B

5. Quick Check:

   Secure boot first, verify, install, rollback [OK]

Hint: Enable secure boot first, then verify before install [OK]

Common Mistakes:

• Installing firmware before verifying signature
• Enabling secure boot after installation
• Skipping rollback support