26 ms·
> embedded field [...] companies should be [...] compelled to release their embedded keys and source code awesome! my botnet malware that exploits and roots yo
by grkvlt 9y ago
> embedded field [...] companies should be [...] compelled to release their embedded keys and source code
awesome! my botnet malware that exploits and roots your smart meter or set top box can now install new firmware with a permanent backdoor and nothing will complain because all the malware binaries are signed - by the manufacturer's key, no less - so they must be secure, right?
- M_Bakhtiari 9y agoIt would be beyond retarded to use the exact same key for every unit. That's not what people are asking for. People are asking for keys to their exact units so they and only they can sign software for them.
- evancox100 9y agoWhile GP's snark is uncalled for, he is correct as that's exactly how this works. What you're asking for is like saying that a web server would provide a unique HTTPS cert to every distinct visitor.
- M_Bakhtiari 9y ago>What you're asking for is like saying that a web server would provide a unique HTTPS cert to every distinct visitor. It's not similar at all. The equivalent would not be the certificate but the session key, and you do get your own session key in order to prevent what the person above is describing. My HN session key is useless for decrypting your HN password even if I could intercept the traffic. There is no technical reason why the devices can't ship with not only the manufacturer's public key, but also a key pair generated for each unit that comes off the assembly line for the customers to use to sign their own firmware images (and if they wish, delete the manufacturer's public key). But they will never be able to sign images for any device but their own because they simply don't have any signing keys that can produce a signature that will be accepted by any device but their own.