Tesla responded by disabling the car's ethernet port, downgrading the firmware, and preventing the car from receiving future upgrades to software.
Tesla responded by disabling the car's ethernet port, downgrading the firmware, and preventing the car from receiving future upgrades to software.
There is this ex-employee, telling some interesting stories. And regarding the downgrade... he was the one who did it for reasons he explains. I want to see if you are talking about different case or what.
> Question: There's the story online of that hacker who was pulling software images off through the door Ethernet port and found that his car's firmware was remotely downgraded after he uncovered and posted the first references to the P100 models.
> Answer: yup, i'm the guy that installed the older versions. this was a marketing mistake really. if i recall correctly, he ended up getting a marketing car or his car got tagged in the update system as a trusted car and he ended up getting pre-release stuff. this happened from time to time - sometimes marketing would sell off a car and the poo poo erp system wouldn't record the change. that car would then get prerelease and sometimes very broken firmware. i seem to recall another case where we just forgot to remove the prerelease materials from the official build, so all you had to do was look around.
https://forums.somethingawful.com/showthread.php?threadid=38...
one big reason why i'm not particularly thrilled at the prospect of one day owning a car that is actively managed/controllable by the manufacturer.
in the days of the audi 5000 sudden acceleration syndrome, they could take a production car and study it.
how would a third party/government agency trustlessly investigate "brake lose control" when the manufacturer has root and remote access on the vehicle?
Ditto.
So many examples of companies shoving half-baked software updates down our throats... and worse... companies with half-baked security that are compromised with no consequences/little liability and effect the consumer.
Is this not already the case?
a) a specific set of source code was used to generate the logs... so cryptographic security from source text files through compilation to execution on the hardware.
b) that specific set of software was run on a specific machine at a specific time.
it's hard... but beyond that, pretty much all audit logs are just security theater anyhow. sometimes can be mitigated by sending them to multiple places, but they're still meaningless unless you have a proof of what exactly generated them.
Volkswagen tampered with regulated measurements and got away with it for a while. But it was discovered and they paid a huge price for it.
With that precedent, it should create incentive to deal with mistakes transparently.
It does also mean transportation authorities will need to create some amount of leeway for mistakes. But I think there has been plenty of that given to traditional auto manufacturers.
1) unassured/untrusted digital evidence that can be fabricated to say anything, leaving no trace of its previous state. (unless digital forensics has advanced well beyond what i know to be possible)
2) personal testimony that can also be fabricated.
i suppose what's new here is that in a digital world, bits can be set however one likes with no trace of their previous state, where physical evidence left behind physical manifestations of itself.
imagine rootkits that seek not to steal or hide their existence, but rather exist to plant fabricated evidence or hide actual evidence. in today's untrusted computer systems, this is all possible, and terrifying.
The first smashing can be felt more than heard, a subsonic strike something like a vast drumhead being struck with a metre-wide mallet, but so quick, you barely even notice it until it’s over. The second one, however, isn’t far behind, and it’s a bit louder. That second thump gives away its location — whatever it was seems to be happening quite close by — in the direction of the parking structure.
At just this moment a car cruises through the pick-up zone at full speed, barreling along at least 100 kmh. It’s only because of some very fast reactions that no one gets hurt as it passes by. As it zooms past, you notice there’s no one behind the wheel.
Before you have any time to process that, another huge thump nearby causes a section of the barrier wall of an upper floor of the concrete parking structure to shear off. A pile of rubble falls to the ground not very far away from you.
-- Mark Pesce, Oct 2015, https://medium.com/@mpesce/the-great-hack-part-one-attack-70...
(Incidentally, I applaud the top comment at [0]. Everyone involved in recklessly demonstrating the hack on public roads, should have faced serious consequences. As far as I can tell though, nothing came from the police report.)
(AI-controlled cars feature prominently as weapons.)
It's only if you aren't logged in to an account that word filters are applied (and some other things e.g. there are a bunch of subforums not visible to outsiders).
https://www.vrt.be/vrtnws/nl/2020/11/22/onderzoekers-ku-leuv...
https://electrek.co/2019/01/29/tesla-sales-ban-sweden-over-s...
Do you have more information on this? The way you describe sounds like it's targeted at aftermarket mods more than software updates.
Obviously different case, but I think the same principle applies here. A software update that significantly changes the performance characteristics should be recertified and not grandfathered in.
sounds like a win-win