Open hardware, quickly becoming a requirement for this little black duck…
The more I read about unpatched crap from fire-and-forget vendors that think once the device hits the manufacturing line it's time to move onto the next product and forget about supporting what they already produce… the more I think that in future, it'll be a personal requirement that the device is shipped with suitable documentation and firmware.
The reason for this is simple.
I, as a home network operator, am responsible for the emissions my network produces.
If a HTTP GET request for a JPEG with kiddie pr0n is seen from my ADSL connection, is it the vendors of the various devices that gets the blame? No, it's me, and then it's up to me to investigate how that HTTP GET request came to originate from my connection.
If a wireless router starts emitting crap out-of-band… is it the router manufacturer that takes responsibility? No, the ACMA will be knocking on my door first. I then have to play a game of unplug-until-the-noise-stops to find out the culprit.
It is high time that, if we are as end users to carry this RESPONSIBILITY, we should be given the RIGHT to audit. That includes being able to FREELY ACCESS the firmware source code, device schematics and other supporting documentation, and FREELY DISTRIBUTE such items to third parties for the purpose of audit and analysis.
The day of the proprietary black box is over.