Re:Fiat Chrysler recalls 1.4M cars after Jeep hack
by vvanders on Friday July 24, 2015 @12:16PM
(#9943011)
Pretty sure Tesla signs their OTA updates.
[ Parent
| on HN ]
Re:Fiat Chrysler recalls 1.4M cars after Jeep hack
by timdiggerm on Friday July 24, 2015 @12:27PM
(#9943109)
Not that that's perfectly secure
Re:Fiat Chrysler recalls 1.4M cars after Jeep hack
by cwyers on Friday July 24, 2015 @12:40PM
(#9943203)
Yeah, it's only as secure as Tesla's ability to secure its private key.
Re:Fiat Chrysler recalls 1.4M cars after Jeep hack
by mikeash on Friday July 24, 2015 @12:56PM
(#9943369)
And their ability to verify the signature on the car. Even if the private key is totally secure, you could either find a weakness in the signature verification, or find an exploit that lets you bypass it entirely.
Re:Fiat Chrysler recalls 1.4M cars after Jeep hack
by UnoriginalGuy on Friday July 24, 2015 @02:02PM
(#9943924)
That's an extremely rare vector for exploitation. I can think of one specific case where a vendor completely forgot to check the result of a signature check, but aside from that signature checking is well understood and rarely goes wrong.
But to be honest people are taking their specification and dooms-day-ism to stupid extremes. Soon we'll be talking about "it is only as secure as the CPU, what if you find a CPU bug and bypass all security?!"
Re:Fiat Chrysler recalls 1.4M cars after Jeep hack
by ZoFreX on Friday July 24, 2015 @02:37PM
(#9944210)
> signature checking is well understood and rarely goes wrong
I would argue otherwise, plenty of signature schemes give you enough rope to hang yourself. The Playstation 3 example springs to mind!
Re:Fiat Chrysler recalls 1.4M cars after Jeep hack
by pigeons on Saturday July 25, 2015 @12:48PM
(#9948138)
Signature verification for android applications has been a tough one: http://www.saurik.com/id/19
Re:Fiat Chrysler recalls 1.4M cars after Jeep hack
by takeda on Friday July 24, 2015 @01:44PM
(#9943787)
There's plenty room for bugs in mechanism like that. For example Motorola Droid (back in 2010) was locked and only accepted signed updates. There was a bug where you could bypass it by using authentic update and appending your payload at the end of that file.
Re:Fiat Chrysler recalls 1.4M cars after Jeep hack
by thesteamboat on Friday July 24, 2015 @02:01PM
(#9943917)
Interesting, can you point me to a news article or link? Shouldn't that have been rejected as an improperly signed file as (update+payload) should have a different signature than (update)? I'm want to know whether I'm misinterpreting something, misunderstanding something, or the signatures were misimplemented.
Re:Fiat Chrysler recalls 1.4M cars after Jeep hack
by takeda on Saturday July 25, 2015 @02:40AM
(#9946785)
The original forum where it was posted doesn't exist anymore and there doesn't seem to be archived copy.
Here's another page which is describing the steps: http://www.areacellphone.com/2009/12/motorola-droid-rooted-h...
Here is the commit with a bug fix: http://review.source.android.com/12807
and actual diff: https://android-review.googlesource.com/#/c/12807/1/verifier...