dll and market.

New comment
 

IV. Продукты

  1. A Product submitted for sale via the Market service may be submitted as a compiled file with the extension EX5 or a single source code file with the extension MQ5.
  2. Product files submitted as MQ5 files are automatically compiled.
  3. The Products do not call any DLLs, including Microsoft Windows system libraries.
  4. The sale and distribution of any malicious Products via the Marketplace service is prohibited.
  5. Seller may distribute Products via the Market service on a free-of-charge basis (free of charge).
  6. The minimum fee for a Product that can be offered for sale in the Market service is $10.
  7. Products purchased through the Market service are non-refundable.
  8. An individual secure version of the Product is automatically created for each Buyer, which allows using it only on the hardware (computer hardware configuration and operating system type) from which the purchase request was made.
  9. The purchase of the Product is recorded in the Buyer's account.
  10. The fact of creating a secure version of the Product for Buyer's hardware configuration is called Activation.
  11. After the purchase of the Product, the Buyer is entitled to two free Activations on other equipment.
  12. The names of the input parameters, all messages and screenshots in the Product description shall be in English.

All dll calls are prohibited in the marketplace.

Ok. How about to do the following:

1. The product itself is placed in the market.

2. The part of the code responsible for referring to the dll (win api), put it into a library and put it in codebase. The code may even be in source code.

The main point is that it is necessary to use FileMapping in the product, it is impossible without it.

 
joo:

The point is - you have to use FileMapping in the product, you can't do it without it.

There are doubts that there is no way...

In general, it looks ok, but it's better not to ask here, but probably in the service Desk.

 

The programmes in the marketplace must be fully functional and operational.

The requirement for additional components is unacceptable.

 
Renat:

The programmes in the marketplace must be fully functional and operational.

Requiring additional components is unacceptable.

Gee-goo, we'll kick your ass (just kidding).

Make a program fully operational and functional(eg drawing a daisy on the chart), and add that when you install free Dll, it also trades (by the way you can not add this in the market and when publishing Dll).

All according to the rules, the declared functionality works.

Would you miss it?

PS this is a clever trick, better make your own analogues of Win API, that won't harm anything under control (controllable wrappers), then both people feel better and you will get a medal.

 
Urain:

Gee-goo, we're going to kick your ass (just kidding).

We will make a fully working and functional program(for example, drawing daisy on the chart), and add that when you install the free Dll, it also trades (by the way you can add this not in the market and when publishing Dll).

All according to the rules, the declared functionality works.

Do you miss it?

PS this is a clever trick, better make your own analogues of Win API, that won't harm anything under control (controlled wrappers), then both people feel relieved and you get a medal.

When we find it, we'll ban it.
 
Renat:

The programmes in the marketplace should be fully functional and operational.

You also have libraries, in theory you could do the opposite.
 
Renat:

The programmes in the marketplace must be fully functional and operational.

Requiring additional components is unacceptable.

Renat, knowing your negative attitude towards going beyond the MT sandbox, let's put it this way:

- a marketplace product needs at least a TERMINAL for the product to be fully functional working.

But you're limiting us within the scope of the WinApi functionality you've implemented in the terminal.

It's irrational to nag the MC from our side to add some special winapi function to the MQL natively.

That's why we're nagging for permission to call the winapi dll for marketplace products.

Calling winapi - in no way will make the product non-functional and non-working.

--------------

You promised to look at the marketplace after its launch.

Time has passed, please look at the market from this side.

I think that winapi challenges on the contrary will bring to the market professional programmers with their products. And that's +20% in MK's pocket.

 
TheXpert:
You also have libraries, theoretically you could do the opposite.
So you propose to do the opposite - sell ex5 libraries in the market and put dummies + dlls in the codebase?
 
sergeev:
So you're suggesting the opposite - sell ex5 libraries on the market and put dummies + dll in the codebase?
Renat:
When we find it, we'll ban it.
 
Renat

Just make a Win API pad, which would catch non-hazardous libraries.

After all, not all of them are potentially dangerous (those which you consider dangerous are in fact very few).

 
Urain:

Just make a Win API pad, which would catch potentially dangerous libraries.

After all, not all of them are potentially dangerous (those that you consider dangerous are in fact very few).

No.

We are fundamentally against the proliferation of DLLs and the creation of mass threats to traders. On the contrary, we are now working to curb the chaos that some companies have been whispering.

There are no "insecure" DLLs. Virtually any DLL (including system DLLs, almost all of which are infamously insecure) can be used to perform a stack-skipping attack followed by a control takeover. All it takes is the illusion of security in the form of trusted DLLs, and the security will immediately fall to the bottom of the barrel. For all the good developers will demand that incompetent users include their creations in the allowed lists. They don't care about anyone's recommendations or traders' safety, because all they care about is money.

We will not turn a critical system into a hole like Microsoft's solutions.

Everyone is free to use whatever they want for themselves, any DLL. But you may not distribute potentially dangerous code through our (including brokerage) channels.

1234567
New comment
Reason: