The ISTA+ manual says that "enabling codes" are either downloaded from some online server, or if that's not possible they can be imported manually. I'm wondering, if anyone has an example "enabling codes" package that can be imported manually and would be willing to share it? They should be available in the Aftersales Assistance Portal as zip files.
My line of thinking is, if we can reverse engineer the "enabling codes" package, we might be able to start creating our own "community enabling code" packages that can be executed with ISTA+ & contain everything needed for a single functionality.
For example, video in motion community enabling code would modify both, SPEEDLOCK_X_KMH_MIN, SPEEDLOCK_X_KMH_MAX and ensure the handbrake one is disabled as well. It could then be enabled/disabled through ista+ as a package.
I did a quick search around the topic and it doesn't look like anyone has investigated these packages before. Tbh, i have no idea about the format of these files, or any possible limitations coming from ISTA+, but this seems like a nice logical avenue to try and improve the process.
edit: looks like the enabling code package contains a ".der" file, which is most probably a certificate signed by a private key from BMW. My guess is, ISTA is checking that against a public key and checks if they match. Now the prerequisite to any reverse engineering would be, where is the public key stored and can we change it?
51.2 KB Views: 154