News for hackers. Stuff that matters.
Re:Pwn2Own Vancouver 2019: Tesla, VMWare, Microsoft, and more by rootusrootus on Tuesday January 15, 2019 @10:29AM (#18911797)
The ability to remotely patch a car seems like a double edged sword. Hasn't Tesla already had at least one example of introducing a bug through OTA updates?
Re:Pwn2Own Vancouver 2019: Tesla, VMWare, Microsoft, and more by HeyLaughingBoy on Tuesday January 15, 2019 @10:32AM (#18911827)
I consider that an issue with the software quality, not with the update mechanism. The bug would still have been introduced even if it required a trip to the dealer to plug in a programming cable.
Re:Pwn2Own Vancouver 2019: Tesla, VMWare, Microsoft, and more by falcolas on Tuesday January 15, 2019 @10:38AM (#18911871)
At least, when it's updated by a dealer and a cable, you know when to expect changed behavior. With OTA, the vehicle's driving behavior could (and has) quite literally change overnight.
Re:Pwn2Own Vancouver 2019: Tesla, VMWare, Microsoft, and more by HALtheWise on Tuesday January 15, 2019 @10:56AM (#18912034)
I'm pretty sure you still need manual confirmation in the car, and it shows you patch notes when you next get in, so you should have reason to expect changed behavior.
Re:Pwn2Own Vancouver 2019: Tesla, VMWare, Microsoft, and more by close04 on Tuesday January 15, 2019 @11:32AM (#18912354)
The only problem I can see with the OTA updates is that they remove the need for physical access to the car. This is very convenient and allows for fast updates but it does slightly decrease the security and lowers the bar for successfully hacking the car remotely.
Re:Pwn2Own Vancouver 2019: Tesla, VMWare, Microsoft, and more by stanmancan on Tuesday January 15, 2019 @10:34AM (#18911846)
That same bug could have been introduced whether or not the update was OTA. At least they could fix it OTA as well...!