This seems sound. However, I'm in doubt about some of their points: > You can ask it to dump the current firmware to you It can dump the firmware but it can still execute something else than this (or in addition to) this firmware, can't it? > You can see all the components on the board The fact that I can see these tiny thingies doesn't do much good either? Can I, seeing them, tell what they do? No. Building one of t…
Note: I'm Paul the designer You're completely right someone could put some other firmware on the image but have it return the correct one - we solve this by: - padding the image to the size of the ROM (256k, the runtime image is ~10k)with random data making it incompressible - signing the image (including the random bit) so that the image can't be altered On a linux system the udev install script kicks off a process…
padding the image to the size of the ROM (256k, the runtime
image is ~10k)with random data making it incompressible -
signing the image (including the random bit) so that the
image can't be altered
You could pad it with data that looks random, but is secretly compressible. For example, the output of a prng with a known seed.Why not pad it with something that's already compressed, but which has information content, like a nice jpeg or something?