I am not sure how long will it take before you will not be able to buy a vehicle at all without having to consent to being monitored remotely 24x7, but it will happen sooner than later. And this coming from a developing country. Pretty sure it is much worse in the developed world.
I guess the market for second hand older vehicles might see an uptick because of this and might also see a boom in demand for expertise of maintaining and rejuvenating such vehicles.
The only module that was encrypted was the main module, but it if you knew the security PIN you could do what you wanted. It was determined by people that if you observed the jitter of the CAN line fast enough, you could leak the pin via a side channel attack.
But modern car electronics are encrypted, and some probably have security processors that might trigger some irreversible states if you tamper with them. Modern cars are basically as locked up as a PS5.
How do you expect the aforementioned tech to break the games it's on? If anything it "breaking" will just make the anti-tamper feature ineffective.
Such was the case for SecuROM in early days. It featured the CRC checks mentioned, if any single byte was changed, including an INT (breakpoint) instruction, it would crash. Here it's unlikely that it wont crash. Rendering the game inoperable.
I would imagine many things from the SecuROM era live on in Denuvo.
But if you read the article you will realize that certain games will not work in the future due to Denuvo.
"This destroyed any exception-based hooking since majority of the time an exception is triggered, Windows will write an EXCEPTION_RECORD high up in unused stack space. You can probably see where this is going. Now, whenever the CPUID is hooked via an exception, that important value will become overwritten with an EXCEPTION_RECORD, causing undefined behaviour later on. I believe this can be bypassed if you attach a debugger to the process and set certain flags when it comes to exception handling, but the method of patching every hardware check is still cumbersome due to randomness anyway."
As Windows matures, behaviour can change, breaking certain stuff.
But it requires for me to not only reverse engineer, but potentially also modify the firmware of my ABS unit to allow it to brake, which I am not comfortable doing.
I like Fluent by MS far far better than this.
I spent 1.5+ years on my 2005 car's ECU to reverse engineer most of the maps, since no public tuning files existed. I then went and spent 1 year on the TCM for which again, no tuning files existed. With the patent files, I was able to discover the algorithms and maps, and am even in IDA as I write this, and in Ghidra emulating some code.
What changes have you made?
To say I am the only one with such a complete understanding and tuning abilities for it, may not be an understatement.