←back to thread

Tesla said it didn't have key data in a fatal crash, then a hacker found it

(www.washingtonpost.com)
650 points clcaev | 1 comments | 29 Aug 25 11:15 UTC | HN request time: 0.209s | source
Show context
fabian2k ◴[29 Aug 25 12:38 UTC] No.45063298[source]▶
Do I understand it correctly? Crash data gets automatically transmitted to Tesla, and after it was transmitted is immediately marked for deletion?

If that is actually designed like this, the only reason I could see for it would be so that Tesla has sole access to the data and can decide whether to use it or not. Which really should not work in court, but it seems it has so far.

And of course I'd expect an audit trail for the deletion of crash data on Tesla servers. But who knows whether there actually isn't one, or nobody looked into it at all.

replies(7): >>45063548 #>>45063617 #>>45064088 #>>45064532 #>>45065580 #>>45067599 #>>45069859 #
Someone ◴[29 Aug 25 13:00 UTC] No.45063548[source]▶
Another reason is if there’s other kinds of data that gets uploaded to Tesla, and the code for uploading crash data reuses that code.

For the first kind of data, deleting the data from the car the moment there’s confirmation that it now is stored at Tesla can make perfect sense as a mechanism to prevent the car to run out of storage space.

Of course, if the car crashed, deleting the data isn’t the optimal, but that it gets deleted may not be malice.

replies(3): >>45063636 #>>45063757 #>>45070858 #
1. ndsipa_pomu ◴[30 Aug 25 00:25 UTC] No.45070858[source]▶
I've got front and rear cameras on my bicycle and both of them have a simple crash protection feature. If the cameras detect the bike falling over, they'll mark the current video segment (typically split into 5/15 minute segments on the SD card) as protected and won't be overwritten when the SD card fills up which is the usual operating mode.

If Tesla are marking crash data to be deleted, then that's not designed to help the customer, but to protect Tesla.