3 ms·
If their stage 1 is verifying the signature it's going to be pretty hard to hack the firmware (since you need to crack the key or find some other hole to get yo
by peterwwillis 14y ago
If their stage 1 is verifying the signature it's going to be pretty hard to hack the firmware (since you need to crack the key or find some other hole to get your firmware to run), so at that point they could care less about logging in to double-check the key wasn't cracked. In that case the integrity check is more likely just making sure the firmware isn't corrupt, or just checking the version to see if it needs an upgrade in general. If on the other hand they are just verifying which firmware is applied, the stage 1 probably isn't verifying the signature, so in that case we really could fake out the check.
Flashing the chip directly is probably significantly easier than attacking the UI's signature verifying feature. Once you learn how it's pretty fun to examine random devices' firmware directly ^_^
- trotsky 14y agoYeah, glancing at the specs it looks like you're almost surely correct, that it's just checking a version string thats returned. I got a little carried away, but really my point wasn't that it's impossible to avoid the risks, just that undoubtedly 99%+ of their customer base could be subjected to this and im sure most don't realize it. I thought my concerns with it were pretty tin foil hat until reading this story about the exact company doing something very, very similar.