<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Firmware Signing on TiJet</title><link>https://www.tainuohc.com/en/tags/firmware-signing/</link><description>Recent content in Firmware Signing on TiJet</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 22 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.tainuohc.com/en/tags/firmware-signing/index.xml" rel="self" type="application/rss+xml"/><item><title>Secure Boot and Firmware Signing: A Practical Guide for Industrial IoT Devices</title><link>https://www.tainuohc.com/en/blog/2026-07-22-industrial-security/</link><pubDate>Wed, 22 Jul 2026 00:00:00 +0000</pubDate><guid>https://www.tainuohc.com/en/blog/2026-07-22-industrial-security/</guid><description>&lt;h2 id="1-why-bother">1. Why Bother?&lt;/h2>
&lt;p>In industrial control, a compromised firmware image isn&amp;rsquo;t just a data breach — it&amp;rsquo;s a physical safety hazard. A tampered firmware could disable watchdog timers, override thermal shutdown thresholds, or silently exfiltrate proprietary motion-control parameters.&lt;/p>
&lt;p>Yet most industrial IoT devices ship with JTAG left open and firmware images verified by nothing more than a CRC32 checksum. CRC32 catches bit flips; it does nothing against a motivated attacker.&lt;/p></description></item></channel></rss>