3 ms·
> If you are easily able to change the firmware, you are easily able to destroy the hardware, and if that's under warranty, companies are going to be concerned
by JohnFen 4y ago
> If you are easily able to change the firmware, you are easily able to destroy the hardware, and if that's under warranty, companies are going to be concerned.
I don't think this reasoning makes any sense. The company can just declare that replacing or altering the firmware voids the warranty.
> I would kind of hate handing that over to potential competitors.
But you do that the instant that your product ships. I've shipped a lot of firmware in products, and it's very common to find my firmware reverse engineered and available within a month or so of the product being released.
- crazygringo 4y ago> I don't think this reasoning makes any sense. The company can just declare that replacing or altering the firmware voids the warranty. It's still a cost, though. People are still going to file tickets for warranty replacements, it won't be until the company receives the broken item that they'll detect the firmware replacement (if they even can, what if the hardware damage broke the ability to check?), people return items to the store they bought them from where they can't even check... It's honestly a whole mess that will absolutely wind up costing the company money in support and returns. You can argue that it's still worth the cost, but just declaring that altering the firmware voids the warranty doesn't stop people from trying, which costs money.
- JohnFen 4y agoYes, it is a cost. I would argue that it's a reasonable cost of doing business, personally, but it is a cost.
- shadowpho 4y ago>The company can just declare that replacing or altering the firmware voids the warranty How can they know/figure it out? (They can't/or it's prohibitively expensive/difficult). >it's very common to find my firmware reverse engineered and available within a month or so of the product being released. Sure, but it's hidden from 99.99% of your user base
- terribleperson 4y agoPrusa (makers of the Prusa 3d printers) set it up so that you had to physically break part of your printer before you could flash custom firmware.
- yjftsjthsd-h 4y agoYou could also just blow a fuse; we do actually have ways to do write-once memory for this kind of thing
- nomel 4y agoCould you describe a rough implementation, with the assumption that the vendor can still provide firmware updates?
- folmar 4y agoYou 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.
- yjftsjthsd-h 4y agoSure. 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.
- crote 4y ago