Re:Software Updates for IoT Devices and the Hidden Costs of ...
by dozzie on Friday January 19, 2018 @05:25AM
(#16185255)
> I say FUD because I see helpful blog posts promoting new tools and software when they should be promoting techniques.
Please do not try to redefine the meaning of an existing term. "FUD" already has its well-known meaning, different than what you tried to use it as: https://en.wikipedia.org/wiki/FUD
Seriously those stack diagrams are massively overkill designs for OTA update infra.
As for your specific points, I left out a LOT of detail.
Yes, or no, depending on your bootloader. GRUB and others can chainload to other partitions after control is given. Of course you'll need to think about how to re-provision user-specific data, though the first idea that pops in my mind would be to simply read it from the old install on first boot. (IRL we are solving this with a first-boot 'activation' app, which re-downloads user data on completion) yes, but this is way easier than needing to learn and roll out someone else's complicated piece of tech. An API server that can receive updates from the field and download scripts/run the commands to start the process.Also, if you've been supporting this kind of product for a while you probably already have your own infra.
of course. Though, if your hardware is uniform you can get away with a lot less of this than one might think, due to the updates being image-based and not package-based. Easiest way is to simply compute a SHA-hash on the download to make sure it wasn't corrupted (make sure the value you compare it with came from a trusted conversation with your server). If it fails to boot the newly provisioned code needs to know to re-point the bootloader at the previous install, though again with uniform hardware your main concerns are transport-related. Fairly trivial with pgp et al.