Anyway, you can already mess with modern cars tire pressure sensors, when driving near them. http://www.winlab.rutgers.edu/~gruteser/papers/xu_tpms10.pdf
Closed source and un-modifiable car firmware is like closed-source crypto and other systems - it's not the best. Because it doesn't really have to be better, so why bother. Open source / custom can be as bad or worse, or it can be much better.
I prefer a world where we have the freedom to have good stuff.
Seems you have broken this rule:
See the following computer bugs that caused safety problems:
* http://www.bloomberg.com/news/articles/2014-07-10/honda-reca...
* http://abcnews.go.com/Blotter/toyota-pay-12b-hiding-deadly-u...
there are dozens of other stories.
If safety trumps all, we might as well ban people from changing their tires. If you don't use a torque wrench, you might find your wheel coming off on the freeway.
It sure would be nice if I could go in and put Google maps in there.
In the long term, tires, filters, and brake pads could become proprietary in the same way as Keurig's K-Cups are now, though I imagine with more complex DRM.
First of all it would be EXTREMELY hard to nail down a car crash to malware currently because we have no tools/insight to do so. For all we know (put's on tinfoil hat) car hacking has been employed multiple times by state actors to kill off people who they disagree with. It's way too easy to write it off a the driver made a mistake and never have an investigation into the root cause.
However we HAVE seen that it's possible to hack into a car, there are multiple news articles showing people taking over control of cars remotely and killing the breaks, shutting off the engine, pushing down the accelerator, etc.
Also I don't buy the "Safety" argument it's way to easy to scream "Think of the children" to kill off an argument. Hobbyist hackers who want to hack their own cars have to still abide by the laws set out by the government just like a mechanic can't put a car on the road without breaks. I don't see the difference, yes maybe it will make it easier for bad hackers to disable your breaks but they could just cut the break line which would probably be easier (or should be if the automakers take security seriously at all which I would bet they don't).
Killing the brakes on a car would require mechanical interference/sabotage, not just software hacking.
I see no reason why the ability to brake in my Prius couldn't be disabled by sabotaging the ECU, same with steering and acceleration. There's not a traditional transmission either, so I can't just force it into neutral and roll up a hill to stop. There's technically a mechanical linkage in the break pedal to the disc brakes should the ECU fail, but ECU failure and ECU tampering are two separate concerns.
With that said, I'm not overly concerned about electronic attacks on my vehicle at the moment, someone would still need to forcibly enter the cabin, connect to the OBDII port and make modifications to the ECU firmware, not something some jerk could do while we are going down the freeway. I would certainly feel a lot safer if the code running on the ECU was available for the community at large to dissect and inspect, though.
Aside from the exceptions snuxoll mentioned, I can think of two ways the brakes could be hijacked on a car with traditional hydraulic brakes in order to cause a crash.
The first is abusing the antilock brake system to render the brakes less effective. Instead of reducing braking power when the wheels lock, it could be programmed to reduce braking power as much as possible in the event of panic braking at high speed.
The second is to abuse the stability control system now mandated by law to be included on new cars in the US and many other jurisdictions to induce, rather than prevent/correct a skid. Stability control works by selectively applying the brakes on different wheels. Applying one front brake at a moderate level (not enough to lock the wheel and leave rubber on the road as evidence) would look just like an erroneous steering input to anyone investigating a crash as long as the tampering couldn't be detected electronically. For extra evil, use GPS or have an observer trigger it manually when the car reaches a location in which a sudden turn would result in an especially bad crash.
http://www.cbsnews.com/news/car-hacked-on-60-minutes/
More info on Security Now episode 497 if you are interested in hearing the security devs being interviewed.
What will happen instead is, the car's software will be signed and even if you somehow get the sources, you won't be able to run a different version. Just like in tivo.
Getting back to technology, 20 years ago you were able to hack the car with a wrench. Now it's just plain impossible to know what's going on. Hopefully not for too long.
http://www.nytimes.com/2010/05/14/science/14hack.html?_r=1
The study referenced [PDF] http://www.autosec.org/pubs/cars-oakland2010.pdf
This was a simple search: "malware car software." Pretty sure disabling the brakes or selectively braking individual wheels on demand could have a deadly impact on auto operation.
So you won't have any problem in <x> years if all PCs are coming with default configuration 'cause "safety trumps all' and "you don't need to tinker with the auto software". You don't need to change your shell. You don't even _need_ a shell anymore. The _company_ will provide you with everything you need. And of course, no choice for what OS you're going to install.
I imagine an answer would be "but my PC isn't going to run over a child". No, but an insecure OS can cause you to lose all your credit balance and many more (which I imagine you can guess being an hn member). All that just because "you don't need to tinker with the auto software".
I'm sorry, but people with views like yours keep the world behind.
"The reach of copyright law has expanded so far that it now threatens people's ability to repair their own cars and protect them against malware. Yesterday, EFF launched a legal campaign to fend off that threat."
Can't even think that I have read any stories (so far) about malware having an impact on auto operation. Hard to believe that opening up the software won't result in something bad happening either.