Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Code stolen threat
Message
De
01/01/2004 20:59:05
 
 
À
01/01/2004 17:40:15
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Divers
Thread ID:
00862748
Message ID:
00863355
Vues:
11
>Good suggestions Alejandro, but the best 'protection' has to be to simply write in VFP in the first place... since there's nobody left (except zealots whose love for the product is irrational and who, by such love, would NEVER steal code) nobody will be able to steal it anyway. < s >

Its actually a good argument, Jim, not just tongue in cheek.

Happy New Year to you. Enjoyed your case study.

Alex

>
>Happy New Year
>
>
>>>Thanks a lot to reply again.
>>>
>>>I agree with you that Refox can decompile whatever can be return in source code like EXE, DLL, FXP, etc. Where through Konxise the main program EXE file can be protected from decompilation and it will reduce in size.
>>>
>>>What I want? I want to protect my any single file that can be fxp, scx, vcx, exe or dll from decompilation.
>>>
>>>Normally I develop one small EXE to start my application and after that I prefer to call my programs individually. So that whenever I will be requested for customization, I can modify and compile only the required file or files instead of whole application.
>>>
>>>Definitely I will buy Refox but I am not sure that it can protect my individual files.
>>>
>>>Regards
>>
>>Abdul, one strategy you could follow in order to continue to use separate files is:
>>
>>1) Encrypt the root program. This must be done as well as possible because it is the weak link.
>>One way would be with Konxise. Another is with HASP from Aladdin, which has a way to "wrap" an application in such a way that it's tied with a dongle. I am sure there are other ways. Require a new root program from time to time.
>>
>>2) Keep all other programs encrypted and set up the encryption before calling each one. I use Cryptor (from the same folks as Refox and Konxise) for encryption. It is very effective with hardly any overhead. All you have to do is make a call indicating the file and password and then go about your business with USE, DO FORM xx, DO REPORT xxx or DO xxx. Cryptor intercepts the file reads/writes at the OS level. It's transparent.
>>
>>Please note that you will need a new fll for each new version of VFP, although I believe there is another way that I can't use because I use an old algorithm. In any case they charge a reasonable amount for the fll.
>>
>>Recognize that you can't get 100% protection, but at least you can get some.
>>
>>Alex
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform