The problem exists in developer tools and languages more recently created like Java and. This problem is not unique to Visual FoxPro developers. It would be nice if the Fox Team would add a key to this algorithm so we as developers can determine how the encryption is set, but this feature is not a priority and could be difficult to implement. Decompiler vendors have broken this encryption so it is a useless setting in our opinion. Microsoft has provided the ability to encrypt the application when the executables are built. On the up side, if you have a catastrophic hardware failure or the developer ‚ s computer is stolen and all the backups of the source code are bad (or not current), but you have a recent copy of the executable, you can use one of these products to partially restore the source code.ĭevelopers have long considered this a problem. If you are deploying a vertical or horizontal market application and another developer decompiles your application, they could steal your intellectual property. Is this a problem? Not if you develop custom applications for clients who buy the source code or have the rights to the source code to make derivative works (see Chapter 12, ‚“Legalese ‚½ for more details on the derivative work topic). Decompilers literally take apart a compiled executable file (APP, EXE, or DLL) and reproduce the source code of the application. This is the case with FoxPro and Visual FoxPro. Decompilers have been around as long as compilers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |