▲ | nine_k a day ago | |||||||
Why, we of course could if we cared. Let the car offer a wifi access point. WPA3 is secure enough, but you can of course have an extra layer of TLS inside it. For the extra paranoid, a car could have a USB socket that pretends to be a wired network interface, offering DHCP. Run a web server for car diagnostics and maintenance when connected to this interface. Do it from the comfort of your laptop, or anywhere anytime using your phone. Zero chance of remote exploits, if you set the things correctly on the car side. An ESP32-based system with $5 BOM would suffice to provide this. | ||||||||
▲ | andrewla a day ago | parent [-] | |||||||
Not with off the shelf protocols. Yes WPA3 is plenty secure, but any AP advertising the same SSID with the same key would allow the device to connect. So how do you know that you're connected to your car, and not to the black hat AP next to it? From there, you can have as much TLS as you want, but that still won't give you server identity unless the server certificate is signed by someone you already trust. So a generic web browser would be screwed, because you either add SlateTruckCertificateAuthority to the globally trusted list, and then you still have to deal with revocations and certificate expiry, or you use some other CA that is willing to delegate. There's no good support for self-signed certificates or pinned certificates, and even if there were, the initial connection would be tough. Unfortunately this really isn't a well-solved problem. Bluetooth can get you part of the way there, but it only offers really good security in theory (in practice it is constantly having issues) and it is intrinsically limited. | ||||||||
|