MQL: security vs opportunities - page 3

 
C-4:
For example, I want to make an indicator that displays fundamental information and macrostatistics and sell it on the market. To do this, I need to collect statistics from several data sources, translate them correctly into numbers and accumulate history. All this is hard and laborious work, and it is done on the project server. Then the indicator is written and placed in the Market.
You can not do this. Read the rules.
 
Urain:

When you buy a license for MT4/5 (you will become a broker), you will be able to include your indicator communicating with your server in the distribution package.

For the rest of us, it's a piece of cake.

Who knows, Renat said: "broker (or third-party developer)" - i.e. anyone who is ready to write client-server application according to MQ rules. However, we really need to clarify.
 
C-4:
Who knows, Renat said: "broker (or third-party developer)" - i.e. anyone willing to write client-server application according to MQ rules. However, we really need to clarify.

Note the keyword "distribution" - this is the MT terminal. If you have a licence for the terminal or the broker has given you access to set up the terminal, then yes.

If you don't have your own terminal, sit back and smoke.

IMHO I see this announcement as MQ's intention to streamline the mess brokers made with co-brand terminals.

ZS sure it's a good idea, but in the context of the topic it seems to have been sidetracked.

 
TheXpert:
You can't do that. Read the rules.
Although, no, it's a double-edged sword. Now I'm wondering.
 
C-4:
Apparently, your project with option levels lacked exactly this announced feature at the time. The story would have developed very differently now.

That's not the reason why the options died. Now I have futures volumes for the real-time CME quadruple, as an official representative. And there are other interesting projects on pure MKUL (without leaving the sandbox (although only for Quartet))...

Let me try to decipher Renate. Everything is still the same, only secure solutions are allowed (in the sandbox). brokers will additionally be able to implement some of their solutions (services, services) with advanced information exchange at the trading server level (again, security). But all the client parts should be on a pure MKUL (and again security).

 
C-4:
For example, I will want to make an indicator displaying fundamental information and macrostatistics and sell it on the market. In order to do that I need to collect statistics from several data sources, translate them properly into numbers and accumulate history. All this is hard and laborious work, and it is done on the project server. Then we write an indicator and place it in the Market. This indicator connects with my server through MT5, gets all necessary information and displays it on the chart. All work on the classification and collection of information falls on the server.

In reality it reads as follows:"I will be able to send any personal and private information from the terminal of any user to any address in the network". And don't say "well, I won't be able to steal the password".

I specifically wrote "every first script is guaranteed to steal private information". And no amount of restrictions will stop programmers from doing so. At first, of course, everyone will swear that they will not do anything wrong, then "just a little for statistics", and in six months there will be an epidemic of spying. Next, there will be black-picture topics about the atrocities in MetaTrader.

It's a trading terminal with access to finance, which has quite serious security requirements. Brokers would be horrified if they suddenly realised that there was a direct and completely easy way to steal private information.

Документация по MQL5: Предопределенные переменные / _StopFlag
Документация по MQL5: Предопределенные переменные / _StopFlag
  • www.mql5.com
Предопределенные переменные / _StopFlag - Документация по MQL5
 
Renat:

In reality it reads like this:"I will be able to send any personal and private information from any user's terminal to any address in the network". And don't say "well, I won't be able to steal the password".

I specifically wrote "every first script is guaranteed to steal private information". And no amount of restrictions will stop programmers from doing so. At first, of course, everyone will swear that they will not do anything wrong, then "just a little for statistics", and in six months there will be an epidemic of spying. Next, there will be black-picture topics about the atrocities in MetaTrader.

It's a trading terminal with access to finance, which has quite serious security requirements. Brokers would be horrified if they suddenly realised that there was a direct and completely easy way to steal private information.

I totally agree, breaking the rules has always given a competitive edge, so if the opportunity is there, there will always be people who cross the line.

Still, I don't believe that there is no solution to how to communicate between different programs in one or more terminals safely (both for the hardware, for the software and for the user).

 
Urain:

IMHO I see this announcement as MQ's intention to streamline the mess brokers made with co-branded terminals.

Exactly.

Not all brokers even realised what kind of Trojan the "conscientious developers" had slipped them. Especially it took a long time to explain that "enable DLL by default for all users" equals opening the gates for any Trojan, which can be simply slipped in as a harmless MQL4 script.

Instead we have offered a completely safe and legal way to extend the functionality.

 
Renat:

Exactly.

Not all brokers even realised what kind of Trojan the "conscientious developers" had slipped them. Especially I had to explain for a long time that "enable DLL by default for all users" is equal to opening the gates for any Trojan, which can be simply slipped in as a harmless MQL4 script.

Instead, we offered a completely safe and legal way to extend the functionality.

Can you at least give me a hint which one ?

Trojan on MQL ? can't imagine... honestly.

 
FAQ:

Can you at least give me a hint?

Trojan on the MCL ? I can't imagine... honestly.

You're not making any sense, the Trojan was in the context of enabling the default Dll for all users.