News for hackers. Stuff that matters.
Re:Hacked Jeep USB update criticised by brudgers on Sunday September 06, 2015 @10:58AM (#10177810)
My understanding of the original hack is that the root of the hack is a flaw in the existing platform validation. In particular that the random seed is set from the clock [not a bad practice in itself] and the clock is activated the first time the car is fired up [a somewhat problematic, since an attacker can be assumed to have the vehicle date via the VIN]. However, it's not even that hard since the first time the vehicle is fired up, the clock is at it's default time and date, and this narrows down the seeds to the range of potential latencies between the clock coming on line and the generation of the entropy pool.

In other words, the USB key can't use stronger crypto than vehicle and that crypto is poorly implemented [again, based on my understanding of the original hack].

Re:Hacked Jeep USB update criticised by NetDissent on Sunday September 06, 2015 @12:32PM (#10178098)
Yep and Chrysler have managed to change the open 6667 IRC channel into a closed one. Without access to that, the hack is now obsolete
Re:Hacked Jeep USB update criticised by tokenizerrr on Sunday September 06, 2015 @04:49PM (#10178953)
These cars use IRC?