Code Protection: New MQL4 language(Build 600+) decompilation protection and other crack techniques. - page 3
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
I was just checking my code and it totally visible in a hexeditor.
How do i protect it? im using newest MT4 build.
Hello slicken,
Can you post a screenshot of what you are seeing?
This is what I see (just the copyright visible, nothing else)
Many thanks
Put your code in a DLL. That's the award winning answer since MQL2.
Hi,
I read about the new mql4(Build 600+) and already updated my EAs, now i have a question. How secure is the new protection against crackers and other types of executable cracking and modifying the code. EX: hex editing date of expiration, memory dumps, etc.. How secure is a simple time restriction(expiration date) on a EA now? How to implement new protection techniques using the new language?
ex:
Thanks
Hi,
I read about the new mql4(Build 600+) and already updated my EAs, now i have a question. How secure is the new protection against crackers and other types of executable cracking and modifying the code. EX: hex editing date of expiration, memory dumps, etc.. How secure is a simple time restriction(expiration date) on a EA now? How to implement new protection techniques using the new language?
ex:
Thanks
You can use YPY MQ4 Code Protector - free online service for encryption and licensing a of source code in *.mq4 format
https://www.mql5.com/en/blogs/post/652126
You can use YPY MQ4 Code Protector - free online service for encryption and licensing a of source code in *.mq4 format
https://www.mql5.com/en/blogs/post/652126
Well, it is not human-readable before compilation, but it tells nothing about the protection. It would be interesting to show a sample of the output from the outdated decompiler, to demonstrate the advantage of the protection. From my first guess it is obfuscated, but i cannot see if it is protected.
Not that we are aware of.
And it is recommended to use the cloud protector service.