[masa52]

does coding 2.0 will be only affecting latest models U or it also affect F and G series??

[Node]

does coding 2.0 will be only affecting latest models U or it also affect F and G series??

It ALREADY affects many G series (just not many units)!!! Just look the ordeal st1 went through. Otherwise - who knows... There isn't any technical difficulty to make all units use secure coding. Just replace signing keys in BTLDs and not include them in offline files.

[Mwahab]

Back to topic - Why when i use ISTA OSS (ISTA online from TIS) I can’t validate certificates automatically, i still must validate the JSON files from ECU validation tab from the site, then import it with Ista or ESYS?

[davidoff86]

This will get you as far as encoding a module, but not sure how it'll work for coding (modifications of NCD) seems ISTA is not permiting any changes to CAF files.

This thread went off topic, but common guys, its the whole REASON secure coding is being introduced - to stop BMW losing money on things they can sell to people in form of subscriptions and FSCs. Of course they say it's about security, but that's mostly the BS for lamers.

I have no access to any secure coding car for tests so don't know how it actually works. But from pure logic if I were BMW then I don't see any reason why should servers (which ISTA contacts) be just signing the locally made NCD. It would make more sense that server prepares NCD and signs it. ISTA just receives it and uploads to the car. Whether ISTA sends actual FA to server or they just use factory FA with official retrofits, that is a different question. Of course there will be servers for internal and supplier use which sign NCDs but I don't expect these to leak to public. If they would - the high number of requests from different IPs will clearly give away leaked account which can be easily removed.

So I would say enjoy while you still can use ESys for custom codings as that is going bye bye.

I'm sure there will be developments like they there are now with tunings and similar things. In the end there will have to be something like bench flashing modified BTLD with modified (hence known) coding keys and then using ESys or custom tool to prepare NCD and sign it with that fake key. Or just bench flashing modified coding. Of course these will be much more involved (and hence expensive) operations.

In the end I don't think CAFDs will even be distributed in PSdZ data so ESys will become even more useless.

This ! to be honest, a lot of things people tinker with are things that won't be locked (hopefully! ) behind a subscription, like changes light colors, durations of things etc. BMW could be helpful here and put them in the idrive menu.

More customisation OEM = less off the books modifications.

look at ios for example, apple saw why people were jailbreaking (aside from the sideloading), and now pretty much all these features are in ios

[Node]

I FULLY AGREE that BMW should be more flexible with many more settings available to be changed (by end user or specialist) than they have now. I also think they should have an official way to reuse a used unit. Maybe through AOS because then they would know exactly who tinkered with the unit and in the case of theft there would be a trail to follow. Now it's fully black market without any traces.

Some times however, settings people modify are mandated by laws so BMW would be breaking them if they would allow changing them easily.

That said unless there is a huge public backlash on this I don't think they will care. But that is doubtful as most of people buying NEW BMWs just don't need this.

P.S. To OP (to stay at least a bit on topic) - I don't know how certificates are handled at dealers Maybe someone with dealer experience could chime in on that.

[sun2334]

does one of the pros already have a solution here...there are already new findings

[Mwahab]

Sorry but i have to wake up this thread, Go to help section in Esys40, and read about the tokens, BMW Backend account, sigining NCD over the internet.
I hope someone get a solution soon.

[Node]

Just from the general understanding of things - there can be NO solution for this. Well, for specific iLevels there can be a solution - signing keys need to leak. How probable is that - I have no idea (probably not that much). But even then it's elementary for BMW to change public keys in bootloader again in a new iLevel.

All other solutions will be to hack units (like tuning now) as keys potentially could be replaced using hardware programming, but frankly coding prices will be through the roof if you need to disassemble the module and so on.