3 ms·
Nobody thinks about the fact that they are "fly by wire", using software to control everything. Who thinks about changing the battery controller to cause a batt
by onion2k 6y ago
Nobody thinks about the fact that they are "fly by wire", using software to control everything. Who thinks about changing the battery controller to cause a battery fire? Or controlling the acceleration to maximum? Or setting off the airbags? Or...
Automotive engineers think about those things. When we drive our cars we're trusting them to have thought about those things, just as we're trusting that the engineer who designed the wheel nuts did his work well enough to stop the wheels coming off, or the engineer who designed the steering linkage considered how we might need to go round corners reliably.
- deleted 6y ago[deleted]
- MaxBarraclough 6y ago> Automotive engineers think about those things Not always. Hacking a vehicle's brakes is no longer the stuff of sci-fi, it's already happened in a poorly-designed Internet-enabled jeep, see [0]. (As an aside, I have no idea why they thought it was acceptable to do their proof-of-concept demonstration while driving at speed on public roads.) [0] https://www.wired.com/2015/07/hackers-remotely-kill-jeep-highway/ https://www.wired.com/2015/07/hackers-remotely-kill-jeep-hig...
- macintux 6y agoThat story made me angry. There’s no way they could have known precisely what would happen when they executed that hack; software has bugs (the whole point of these exercises) and complex interactions between systems cause all sorts of weird behavior.
- leetcrew 6y agosetting aside unforeseen interactions between complex systems, the article seems to say that they deliberately disabled the brakes on a public road, while the jeep was moving! that goes well past a fun prank for a story. irresponsible on the journalist's part too to consent to this. the point could have been made just as well on a private track.
- userbinator 6y ago(As an aside, I have no idea why they thought it was acceptable to do their proof-of-concept demonstration while driving at speed on public roads.) To cause even more outrage.
- Silhouette 6y agoAutomotive engineers think about those things. If that were a reliable safeguard, we wouldn't already have several examples about the behaviour of connected vehicles being compromised remotely in one way or another. Since unfortunately we do have such examples, evidently whatever is going on within the engineering groups at the auto manufacturers is not sufficient to ensure our safety and security in relation to these new generations of connected vehicles.
- yodelshady 6y agoDo they? Ask literally any ICS security professional their main concern, it's "[organisation(s)] think a system is airgapped when it isn't". Whether a system is software-defined/hardware-defined, networked/standalone - these are not technically hard questions to answer, correctly. (No more so than, say, whether polymer O-rings will completely fail to do their job when cold.) That they're not answered correctly indicates a big communication issue, and whilst I'm sure management has much to answer for, I'm not sure engineers escape the blame for that either.
- ensiferum 6y agoThat's the reason why there are standards such as the ISO2626, so when a vehicle malfunctions and causes mayhem the vendor isn't at fault but the standard (assuming that the vendor did meet the standard). And then the blame can be pointed at the standard (i.e. "we did everything by the book not our fault") then nobody is liable.
- goatinaboat 6y agoAutomotive engineers think about those things. Looking at CANBUS, I guarantee that they do not. Any device trusts any other device, access to the bus is the only security control. Connect your entertainment system - probably an unpatched Android tablet - so it can display any info from the rest of the car, instant compromise of everything.