Rivian says “fat finger” caused software update to brick infotainment systems, physical servicing may be required::Today’s cars are more like computers on wheels, and even a seemingly routine software update can lead to unexpected consequences. Rivian unfortunately experienced a “fat finger” mishap with their latest software update, bricking infotainment systems […]
I think it’s also worth noting that “security certificates” in this context are almost certainly there for the purpose of locking the system away from modification by the vehicle owner, which means they weren’t necessary (and indeed, ought to be prohibited by law) to begin with.
Rivian was hoist on their own consumer-hostile petard.
I don’t think so in this context. This is probably more like SSL cert trusting or some private/public key pair.
Based on the fact that the screen is blank, I think @grue was correct. The certificate that tells the system that the infotainment was valid was incorrect, so the infotainment couldn’t load. They used the dev-infotainment cert instead of the prod cert.