this post was submitted on 15 Nov 2023
247 points (98.4% liked)

Technology

59298 readers
4979 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
247
Rivian says "fat finger" caused software update to brick infotainment systems, physical servicing may be required (driveteslacanada.ca)
submitted 1 year ago by [email protected] to c/[email protected]
46 comments fedilink hide all child comments
 

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 [...]

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 1 year ago (1 children)

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.

[–] [email protected] 3 points 1 year ago (1 children)

I don't think so in this context. This is probably more like SSL cert trusting or some private/public key pair.

[–] [email protected] 2 points 1 year ago

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.