Answer the question
In order to leave comments, you need to log in
Sale of open php code, how to protect against resale?
There is a fairly large project on CI, the customer is going to sell it in bulk in the open, the question is whether it is possible to somehow adequately protect against resale? How is it implemented, for example, in Bitrix?
Answer the question
In order to leave comments, you need to log in
the customer was going to massively sell it in the open, the question is whether it is possible to somehow adequately protect against resale?From resale by whom? The customer or those who will buy "it" from the customer?
a fairly large CI projectand despite the fact that CI itself is a rather small project - write your own wrapper with similar functionality instead of it - the lesser of evils (provided that a really large project is written on top of it)
How is it implemented, for example, in Bitrix?In Bitrix, this is implemented with the help of:
Translate into open source with a license, at least there will be some protection of rights, and in fact no means will help
In Bitrix: You
buy a key to the site. If a key is exposed on more than 1 site, it is blocked (the key). Without a key, you cannot update the platform or install applications from the Bitrix marketplace. For Bitrix, this is very important because it is Bitrix.
And a question to the question: how does the CodeIgniter license work?
As Alexander Aksentiev quite rightly said - whoever needs it will hack anyway, it all depends on what kind of code. Encrypt - decrypt and hack. If you obfuscate, they will clean it up and hack it. Yes, a full school can and will fall off right away, motivation decides :)
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question