Protecting the source code before compilation - page 5

[Vladimir Suschenko]

Pavel Izosimov:

....The first post states:

"Inthe future, having achieved a high percentage of compatibility of dynamic encryption with various codes, we plan to create a software product with a flexible and convenient built-in secure licensing system (use restrictions by time, account number, owner name, trade server, etc.) that the user can use on their own local computer to protect their source code without passing it on to anyone for this purpose. " ...

It's a false start.
It's like in the proverb: "The chicken is still in the nest, ......., and we've already got oil in the frying pan, about to fry some eggs".
It would make more sense to discuss the product when it is closer to the final state of readiness.

[Pavel Izosimov]

Vladimir Pastushak:

Why is the source code encrypted in the picture? The source code of standard indicator which is in every terminal...

Your method of protection is very doubtful, especially since you haven't attached a code example...

I want to see the encrypted source code of the standard muvin ...

Vladimir, good day!

There are some pictures in the first post:

Example 1. This is what the source code looks like before encryption (file attached)

Example 2. This is what the source code looks like after dynamic encryption (the file is attached)

The MACD Sample primary standard source code files before encryption and after dynamic encryption are attached to the first post

[Pavel Izosimov]

Vladimir Pastushak:

I would like to see an encrypted source of the standard muving ...

Please. Attached is the original and encrypted source of the standard Moving Average.

[[Deleted]]

Fighting the removal of trial and similar protections is relevant, as pieces of this code can be found even in the Nativa without too much trouble.

It is practically impossible to get to the trading logic. Therefore, you don't have to worry about the disclosure of trading algorithms of Expert Advisors. Reengineering (sometimes very useful) is possible only through the history of trades, nothing more.

So, it makes sense to use trash only for functions a la trial protection.

[Rustamzhan Salidzhanov]

everything new is well forgotten old : https://www.mql5.com/ru/articles/1572

[Pavel Izosimov]

Rustamzhan Salidzhanov:

all new is well forgotten old : https://www.mql5.com/ru/articles/1572

Yes, this is a good article, there are others

https://xakep.ru/2010/08/07/54469/

At the end of the day, we create a comprehensive product that can be easily used by anyone, including those who do not have any special programming knowledge at all, e.g. when creating any strategy with a constructor, but the owner wants to seriously secure their code and the protections integrated into it.

[[Deleted]]

I still don't understand why the source code needs to be encrypted?

[Pavel Izosimov]

pako:
I don't get it, what is the purpose of encrypting the source code?

More information on this in the first post

In brief, the purpose is"to protect the source code from unauthorised exploration, modification, renaming and resale".

[[Deleted]]

Pavel Izosimov:

More information on this in the first post

In brief, the purpose is"to protect source code from unauthorised research, modification, renaming and resale".

I'm not giving it to anyone.

[Pavel Izosimov]

pako:
I don't give it to anyone

Do you practice using a VPS for trading?