Launcher V2.6.1 PRO and Premium, NCD / CAFD Tool V0.4.0 Update - Updated 11/08/2016

TokenMaster's Launcher 2.6.0 Premium and PRO are now Out.

[Updated: 11/08/2016]
Launcher V2.6.1 Pro and Premium Builds 130 and 122, respectively, are now out. These updates addresses the initial issues found with the previous releases.

Launcher PRO 2.6.0 Build 128
- Added support for E-Sys 3.28.x
- PsdZdata mapping compatibility upgraded to V3.59.4
- Added color indicator to FDL Cheat Codes (Blue = OK, Orange = partially applied, Red = failure)
- Added FDL Cheat Codes online update
- CAF Viewer is forced to use \Data\psdzdata\swe\cafd folder instead of \Data\CAF
- Changed .NET Framework requirement to V4.5.2
- Launcher is now completely hands-off in coding/flashing modules

- Updated Cheat codes

Launcher Premium 2.6.0 Build 119
- Added support for E-Sys 3.28.x
- Added CAFD Transalation for the following G-Series: G001, G002, G011, G012, G013, G030, G031, G032
- Fixed High DPI/Screen Resolution support for JRE7, JRE8 (E-Sys 3.26, 3.27, 3.28) - Enjoy crisp resolution without down scaling your display
- Fixed issue with HKFM_LS. Older PSdZ library and other ECUs do not need to expand CAF, but HKFM_LS does, and is sensitive to delay. Launcher is now modified to only perform translation when requested from the GUI
- Added color indicator to FDL Cheat Codes (Blue = OK, Orange = partially applied, Red = failure)
- CAF Viewer is forced to use \Data\psdzdata\swe\cafd folder instead of \Data\CAF
- Changed .NET Framework requirement to V4.5.2
- Launcher is now completely hands-off in coding/flashing modules

- Updated Cheat codes

A few notes on these features:

.NET Framework 4.5.2 is now required due to new features added. It can be downladed from this link: https://www.microsoft.com/en-us/download/details.aspx?id=42642

For Premium only. You will be asked to generate a token. I have changed the way token is generated for V2.6.

- CAF Viewer is forced to use \Data\psdzdata\swe\cafd folder instead of \Data\CAF - I find it annoying that the CAF Viewer defaults to \data\CAF. This is one of the more frequently asked questions I get. CAF viewer opens CAF files, FDL-Editor opens NCD files. They don't mix. CAF Viewer now defaults to \Data\psdzdata\swe\cafd, when Launchers are used.

- Added color indicator to FDL Cheat Codes (Blue = OK, Orange = partially applied, Red = failure) - The following picture is self-explanatory.

When previewing or applying changes, the selected item(s) will change color as a visual aide and indicates the status of the code. Blue means accepted, Orange means partially (for multiple code location), and Red means the value is outside the acceptable range.

- Added FDL Cheat Codes online update - FDL Cheat Codes can be updated if it's updated by the author and uploaded to Github repository.

NCD / CAFD Tool V0.4.0 is also now available. PsdZdata mapping compatibility upgraded to V3.59.4  

NOTE: Please do not request via the comment section. I do not monitor the comments actively. Email me at fxxtokenmaster_at_gmail for any question.

E-Sys Launcher 2.5.0 Premium and PRO

E-Sys Launcher 2.5.0 Premium and PRO

E-Sys Launcher V2.5.0 - PRO and Premium are now available


Change Log:

Launcher PRO 2.5.0 Build 103
- Fixed TAL-Editor error on E-Sys 3.24.x
- Enhanced Cheat codes

• Added Series option at the CAFD or code level
• Added Author attribute which can be used as a filter
• Added comment attribute at the function level.

- Enhanced PSdZData mapping algorithm
- PSdZData mapping compatibility is now at V56.5. Some CAFDs are at V57.0
- JRE x64 support. It's now possible to use > 1.8GB RAM. I tested 3.27 and is stable at 4GB. See E-Sys Launcher.pdf for instructions on using 64bit JRE


Launcher Premium 2.5.0 Build 97
- Fixed "High Resolution Fix" option
- Fixed TAL-Editor error on E-Sys 3.24.x
- Enhanced Cheat codes

• Added Series option at the CAFD or code level
• Added Author attribute which can be used as a filter
• Added comment attribute at the function level.

- Enhanced PSdZData mapping algorithm
- PSdZData mapping compatibility is now at V56.5. Some CAFDs are at V57.0

NOTE: Please do not request via the comment section. I do not monitor the comments actively. Email me at fxxtokenmaster_at_gmail for any question.

E-Sys 3.27 and E-Sys Launcher 2.0 PRO

Newest E-Sys 3.27.0 now running on E-Sys Launcher 2.0 PRO. Still Alpha quality but pretty much working. See the following quick demo.

Launcher shown in the video is not out yet, nor is it ready. It will be when I'm comfortable but for now, stick with what you have.

Please do not request download link by commenting. I will not reply to anyone asking me to send the software to them. Thanks for understanding

Why Hacking XMLCrypto is Bad, Really Bad!!!

From the get-go, I've always avoided cracking XMLCrypto. Every time I see a discussion about hacking it, I always say leave it alone. To some people, that came across as protecting my vested interest. That can never be farther from the truth.

I've also been in discussion with a few people wanting to do their own solution, and they always focus on this one class: The XMLCrypto class. I don't blame them. I mean, this is the shortest way to their goal. I mentioned in one of my previous blogs that I looked at this and have almost considered doing exactly just that. But...my training and experience pushed me to find another way. And there's always another way. Working for a top tier security company, I've seen all this happen too often. Bad guys are always trying different things to spread harm. And I love my car too much to have to worry about this problem.

More and more solution are coming out and they're all centered on cracking XMLCrypto. There's one solution that is particularly bad. For one, this was based off of somebody else's work. For another, it entailed patching 3 class files. 3 Class Files!!! Seriously?!? If he knew what he was doing, he wouldn't be patching 3 files. If everyone had at least some sort of basic security training, they'd leave XMLCrypto alone. If everyone cares about their cars and their friend's cars as much as I do mine, they'd leave XMLCrypto alone.

So, why is it bad? For those who know E-Sys, you know that it is only part of a bigger solution. PSdZ (PSdZData) is what makes it work. All files in PSdZ are digitally signed, encrypted and some are even compressed. There's a reason for that. The very reason we digitally sign a document is to preserve its integrity and verify it's authenticity.  When you patch XMLCrypto, you take all that away. You dump the digital signature and accept everything blindly.

XMLCrypto is our last defense in verifying FA, FP, CAFD and everything else. It is our protection from tampered files. Think of it as the firewall of PSdZ. It only allows trusted and verifiable files.

Figure 1: XMLCrypto doing its job

Like I said, patching it takes away all these feature and benefits. It's akin to creating a wide hole in the firewall. Wait, not just a hole, but you're actually breaking down the entire defense wall. Why anyone would do it is well beyond me. It such a shame they don't understand this concept and the danger of doing such a thing.

Figure 2: Patched XMLCrypto Class

Proof of Concept: Download this file: Modified CAFD This is an CAFD, altered and repackaged. Unpatched E-Sys will never accept this CAFD file as it knows it's tampered and will never pass verification. But those with patched XMLCrypto will have no trouble using this file. In fact, the app will gladly accept anything you throw at it.

But what can a tampered CAFD do, you ask? CAFD is a file template which contains things like default values base on your Vehicle Order. Unfortunately, it also contains values for transport mode. What is "Transport Mode"? It's when your car needs a ride to the dealership because it wouldn't start on its own :).

Kidding aside, it is very easy to get these values and replace the ones used as default values, package and distribute it as "New" version of PSdZ. None would be the wiser, certainly, not your patched E-Sys.
 
This is why I didn't patch XMLCrypto. I hope everybody realizes this.