News for hackers. Stuff that matters.
Re:The keys to the keydom by kalleboo on Sunday October 27, 2013 @06:54PM (#6624017)
The post mentions "Most of them are found in embedded networked devices, such as routers and firewalls". Embedded devices like that have very little entropy on first boot - that could might cause them to generate very poor keys.

I wonder how many of the 60% non-unique keys are embedded devices with hardcoded keys...

Re:The keys to the keydom by bigiain on Sunday October 27, 2013 @10:52PM (#6624827)
"I wonder how many of the 60% non-unique keys are embedded devices with hardcoded keys..."

That wouldn't surprise me much at all.

I've been working on a secure workaround to let an embedded webserver on our consumer-oriented wifi-equipped hardware(1) do OAuth2 authentication (to connect to owner's Twitter/Faceboot/et al. accounts). OAuth relies on SSL/TLS to protect it's password-equivalent tokens on-the-wire. Getting an SSL cert onto the device (at a reasonable cost) so that a phone connecting to it via wifi doesn't throw up big scarey "somebody might be doing _bad_ things!" warnings is not easily solved.

(1) Shameless self promotion: http://holiday.moorescloud.com - The world's most intelligent christmas lights…

Re:The keys to the keydom by voltagex_ on Sunday October 27, 2013 @08:17PM (#6624321)
I can see the bumper stickers now - "Have you disassembled your firmware today?"

Sigh. I'm not sure what we can do (as an industry). Bad devices (and bad firmware, and bad software) are so widely deployed it seems almost impossible to fix.