Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

They have remote root access to the vehicle. Even if they didn’t, they can push an update specific to your vehicle that then drives you off a cliff at a designated time.


Updates are not automatic. You choose when to install them. People can and regularly do, wait long periods of time before updating.


> Updates are not automatic. You choose when to install them. People can and regularly do, wait long periods of time before updating.

Says Tesla's software, which can be changed or can be lying.

IIRC, one self-described ex-Telsa firmware guy recounted on some story where he or his team scripted running some SSH commands on a bunch of vehicles to fix some bug they pushed that wouldn't have been able to fix otherwise.


Updates are also not generally delivered via cellular, unless they're classified as critical.

Tesla owns the entire stack. They choose when to update, it just happens to be easier and more pleasant to give people the choice. Given that you can trigger the update via the mobile app, there is clearly support for remote updates. And if you as an owner can do it, then Tesla certainly can, even if they choose not to.


Demonstrably false. Prior to the M3 release, someone with an MS discovered its existence in the firmware.

Tesla disabled his ethernet port in the vehicle, automatically downgraded the firmware to another version which didn't have references, and then blocked the car from getting future upgrades.

-User mode updates- may not be automatic - that does nothing to prove that Tesla cannot update a vehicle without interaction.


Prove it? Link the repo




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: