3 ms·
> firmware developers - learn from these mistakes. Hopefully GCHQ is coming for your code next. I won't be able to sleep tonight, thank you very much... Lucky
by raxxorrax 8y ago
> firmware developers - learn from these mistakes. Hopefully GCHQ is coming for your code next.
I won't be able to sleep tonight, thank you very much... Lucky me I only develop for medical devices. Nobody seem to care about that too much...
But firmware often does carry config-files for many, many different hardware revisions and versions. Creating a binary is mostly more work than just calling ./configure.
This code is never nice code. It is also difficult to implement unit tests. So for efficient testing, you need a good laboratory. With many fancy hardware devices... Additionally, the code was probably meant to never get public.
> these haven't been "universally applied"
This is probably the case for any vendor that existed for more than half a year. To be honest, I can see the criticism, but there will be lacking "hygiene" at least at some cases.
I wouldn't criticize the coders as much as the person responsible to use hardware from a chines vendor for critical infrastructure, that makes this kind of verification necessary.
Why not build your own system then?
- calyth2018 8y ago> Nobody seem to care about that too much... Not until someone in a company has a great idea of hooking that up to the internet insecurely... Basically the medical equivalent of attaching the internet on Jeep's CAN bus...
- raxxorrax 8y agoTrue. That creates sudden interest and with good reason. I don't have much experience with this but colleagues are furious. DICOM is often criticized and I know at least some manufacturers that have questionable security policies for online data exchange. I believe people are happy if it just works somehow, because some applied standards are older than TCP.