Hello, fans of chip tuning and Ghidra.
Today, I'd like to discuss securing your code from the curious.
Once you've written your code for map switching, launch control or any other KAN-related function, you'd probably really like it to be secure enough that it doesn't immediately find its way into the offerings of others who
instead of arriving at concrete solutions, just try to copy the ideas of others.
Securing your solutions is essential. I added a lesson on securing code to the introductory G-Hydra course for Tricor, and there, I presented one of the more interesting and practical ideas for ensuring your code from unwanted analysis.
I'm sure you've heard the words "code obfuscating." Securing programmes written for mobiles or PCs is necessary to prevent information leakage. The same is valid here. Also, a short video introducing the idea of obfuscating code in Tricore will soon appear here. For a full version, I invite you to my Ghidra Tricore training.
