News for hackers. Stuff that matters.
Re:Firmware is on shaky ground – let's see what it's made of by yjftsjthsd-h on Monday April 17, 2023 @03:23PM (#35605272)
You could also just blow a fuse; we do actually have ways to do write-once memory for this kind of thing
Re:Firmware is on shaky ground – let's see what it's made of by nomel on Monday April 17, 2023 @05:40PM (#35606987)
Could you describe a rough implementation, with the assumption that the vendor can still provide firmware updates?
Re:Firmware is on shaky ground – let's see what it's made of by folmar on Monday April 17, 2023 @06:41PM (#35607620)
You have it in any unlockable Android phone.

In short - write the manufacturer public key in ROM and a fuse selects if signature check is enforce.

Re:Firmware is on shaky ground – let's see what it's made of by yjftsjthsd-h on Monday April 17, 2023 @06:53PM (#35607719)
Sure. The vendor firmware contains an option in the settings, "unlock flashing". Enabling this (after a confirmation) will blow the "user modified fuse". When the system boots, the bootloader checks that fuse; if it's blown, then the bootloader will boot any firmware. If not, only boot images signed with the vendor's public key are allowed to boot. When the vendor gets a warranty claim, they check if that fuse is blown; if the fuse is blown and the damage could be software induced, they take that into account (IANAL, but they might not be able to immediately legally refuse it, but they can at least ask pointed questions about what exactly happened; YMMV).

Disclaimer: I didn't come up with this, I'm just summarizing approximately how I understand some Android devices to already work. This also makes me view this system as somewhat battle tested.

Re:Firmware is on shaky ground – let's see what it's made of by crote on Monday April 17, 2023 @07:26PM (#35607989)
You can't read a blown fuse when the entire MCU is toast, though.