3,505 files compiled, 597 shipped
Our firmware needed a software bill of materials for the EU Cyber Resilience Act, but standard tools couldn’t read the image. Working from the linked ELF, I found that only 597 of 3,505 compiled files ship. I also reworked unlock, updates and TLS.
Tracker firmware needed stronger device security, a modern TLS stack and a software bill of materials (SBOM) for the EU Cyber Resilience Act. This page covers the design only. The details stay private.
Which files actually ship?
Standard SBOM tools can’t read this kind of RTOS firmware image, so I worked from the linked ELF instead. Most of what the compiler sees never ends up in the image, and listing all of it would make the SBOM longer and less accurate.
I compared four ways of counting the same build. The compiler saw 3,505 files. The linker’s “unused” list was misleading. File symbols in the ELF over-count by about 2x. Counting only files that own a sized symbol in a loaded section gives 597, and that’s what the SBOM lists. The CI pipeline handles the scanner’s rate limit and uploads to Dependency-Track with CPE identifiers.
Unlock and passwords
Unlocking is challenge-response, and the device verifies a signature. Passwords are stored only as salted PBKDF2 hashes and compared in constant time. Attempt counters survive a power cut. If the lock’s record gets damaged, the lock stays closed.
Updates and TLS
Firmware updates got downgrade and tamper protection, designed together with five new unit-test suites. I shipped it as release owner.
I moved TLS to the library’s current long-term-support line, with TLS 1.3. MD5, SHA-1, DES, renegotiation and DTLS are off. Only AEAD and ECDHE cipher suites are left.
Conclusion
Fail-first unit tests, with fakes for crypto and storage, caught 12 of 12 deliberate mutations. I also ran bench loops with reboots and power cuts.
For security code, a test suite that has never failed doesn’t prove much.