@Petroon362495@joelmarold@elonmusk@TeslaService@Tesla Mainproblem for me is that I was not able to find a firmware dump of the MCU. With that and a lot of time it might be possible to at least understand which code part does update the certificate and from where.
@hackerswagger@yipopov@Petroon362495@elonmusk@TeslaService@Tesla This is irrelevant. This is/was the problem with that hiccup. As long as the OS on the Tesla MCU or other devices what ever you think of trusts the root from eMudhra and does not check revocation it will pass as valid!
@hackerswagger@adam_cypher@Petroon362495@elonmusk@TeslaService@Tesla It seems that this is quiet easy since the eMMC is unencrypted. But the researcher did not check if the image is validated at boot. But the client certs are easy to copy and thus replace. You "just" need to desolder the eMMC from the MCU and solder it on an adapter.
@Johan__Vroonen@Petroon362495@elonmusk@TeslaService@Tesla Do you have access? From how I understand it, the car gets an odin token every 24h. The toolbox uses this token to authenticate to the car. But since the car can't connect to the backend, no new odin token is downloaded. So no way to connect this way.
@2speedy4ya216 Did you test that? Never heard it. Slow charging only happens if the console is off or in Hekate. Beeing in hekate actually drains my battery.
@joelmarold@Petroon362495@elonmusk@TeslaService@Tesla Not possible unless you find a security issue or the firmware is old enough where one is known. SSH to the vehicle via Ethernet is locked with Certificates too. For everything else you need toolbox access to force flash the firmware.