4 ms·
My main concern with HSS is actually not accidental fires. Instead, the HSS are usually all connected to the internet and receive closed-source updates. So if
by dmichulke 2y ago
My main concern with HSS is actually not accidental fires.
Instead, the HSS are usually all connected to the internet and receive closed-source updates. So if a malevolent actor were able to hack into one of these companies (and affect the updates) he could probably cause overheating and/or fires in all connected HSS.
Of course, the damage would be multiplied by the fact that all fires would start simultaneously.
Any opinions on this?
- bArray 2y agoIt's not just possible, but highly likely to occur in the near future. What if the company folds and there is a bug that causes it to halt and catch fire? What stops a RAM/ROM bit flipping? Connected HSS is fundamentally a problem, not unlike IoT. I have several UPS's and not once did I think this might occur, because they are simply not attached to my network in any way. The triggers are based in hardware with a small microcontroller and are unlikely to fail. Systems that run for long periods and could cause damage should be developed differently. Core safety features should be hardware-based, you shouldn't be able to hack it and make it do something dangerous. If it has to be network connected it should be defensively designed.
- GuB-42 2y agoI may be wrong but I think battery protection does not rely on firmware, it may even be analog. There are ICs dedicated to this task, that are cheap and effective. A malicious firmware update can increase battery wear, but it is unlikely to cause a fire.