Re:D-Link publishes code-signing private keys by mistake
by AnthonyMouse on Thursday September 17, 2015 @06:47PM
(#10236555)
> Then there can either be an option to disable this check or a large warning that is produced when you try to install unsigned code.
If the device allows unsigned or self-signed code to be installed then there would be no need to release the signing keys because they are not necessary to make modifications. Releasing signing keys should only be required when it doesn't.
Re:D-Link publishes code-signing private keys by mistake
by michaelmior on Friday September 18, 2015 @12:57PM
(#10240318)
Exactly my point.
Re:D-Link publishes code-signing private keys by mistake
by marssaxman on Thursday September 17, 2015 @07:30PM
(#10236704)
I think it makes more sense to simply forbid automated firmware updates. Put a physical switch on the box; I'll press it when I want to update the firmware. No crypto signature needed.
Re:D-Link publishes code-signing private keys by mistake
by michaelmior on Friday September 18, 2015 @01:00PM
(#10240337)
What about non-technical users who require firmware updates for bug fixes or new features? You can have a physical button, but if the network has been owned in some way, pressing the button could still lead to malicious firmware being installed.
I could see this easily coupled with some social engineering. Control the network and then email users saying that an important update is needed.
Re:D-Link publishes code-signing private keys by mistake
by marssaxman on Friday September 18, 2015 @03:35PM
(#10241554)
Sure, it's no panacea, but it would at least be an improvement over the mess we have now.
Re:D-Link publishes code-signing private keys by mistake
by michaelmior on Friday September 18, 2015 @03:38PM
(#10241577)
How? For the average user (which are who companies really care about), code signing offers an important level of protection. Sure this would be an improvement for technical users who want something hackable, but that's a small fraction of the market.
Re:D-Link publishes code-signing private keys by mistake
by marssaxman on Friday September 18, 2015 @04:01PM
(#10241705)
Code signing is a fix for problems introduced by automatic firmware updates. Intead of going further down the chain by trying to fix the problems with code signing, I'd rather take a step back and find a better fix for the original problem.
Besides, I don't believe that firmware updates need to happen so frequently that there needs to be a convenient way to install them. It's okay if they are a nuisance, because a majority of devices will be updated zero times in their usable lifetimes, and a majority of the rest will be updated one time.
Re:D-Link publishes code-signing private keys by mistake
by michaelmior on Friday September 18, 2015 @04:06PM
(#10241739)
It's not about convenience, it's about security. Regardless of how many menus you have to go through or buttons you have to press if your device will just execute any code that it gets with no way to authenticate the code, you're asking for trouble. At the very least, the device should use a secured connection to download updates from the manufacturer.
Re:D-Link publishes code-signing private keys by mistake
by marssaxman on Friday September 18, 2015 @05:23PM
(#10242135)
How about the device does nothing, and I can download updates from the manufacturer if I choose to? It's my device, not theirs, and I will decide when and if I want to update it.
Re:D-Link publishes code-signing private keys by mistake
by michaelmior on Friday September 18, 2015 @05:27PM
(#10242157)
Sure. If that's what you're looking for in a device. Some users prefer their devices to update on their own. Take Google OnHub[0] for example. They make it pretty clear that new updates will provide significantly enhanced functionality. For users who want a device like that, securing updates is still important.
Then there can either be an option to disable this check or a large warning that is produced when you try to install unsigned code. There's really no point in code signing if everyone has access to the private keys.