>>I see no practical way to enforce that the source code that has been published is actually the same as that running on the car. I was going to say that you c

>>I see no practical way to enforce that the source code that has been published is actually the same as that running on the car. I was going to say that you could dump the code from a random vehicle and compare the hashes. But I suppose that would require having the entire toolchain to go from source to shipped code. >>Not quickly. Perhaps I should've said "more quickly." You've got a point that it's difficult to verify that code doesn't do anything bad. However, it's relatively easy to start from the notion that it's doing one particular bad thing and then find the code that does it, which would've been the case here.